Join this groups for roms and support...
Telegram:
https://t.me/teammaxmtk
Facebook:
https://m.facebook.com/groups/673560846179945?ref=bookmarks
Congrats to every canvas 5 user.
Don't forget to join the official whatsapp group of canvas 5.
https://chat.whatsapp.com/2YtWDoFzukZKthAUenMv74
Plz share the SS of the rom.
Big hit and Thanks to Arshjot singh and Harishwarrior bro... U two are the best dev... Give new soul to MMX CANVAS 5
..
sun75 said:
Hi,
after some debugging, I solved the compass problem (at least on the Wiko Fever 4G). If the Canvas has the same sensor, you have to put a /etc/init.d/30compass script as follow:
---CUT HERE
#!/system/bin/sh
# Adding Ecompass Daemon - By Sun75 @ XDA ####
su 0 setenforce 0
/system/bin/logwrapper /system/bin/akmd09911 &
##############################################
---CUT HERE
Make sure you have /xbin/su in your Rom, but in your's... there is!
Repack the Rom zip, and reflash it (you will lack Selinux permissions by adding with a Root explorer) with TWRP.
At next boot, your Msensord will fail starting the gsensor child daemon, but you will have the gsensor/compass daemon started as a separated daemon fixing the problem!
09-16 21:53:28.249 330 330 D MsensorDaemon: Msensor deamon statr!!!!!!!!!!!!
09-16 21:53:28.249 330 330 D MsensorDaemon: msensor demon start process detect demon name = akmd09911
09-16 21:53:28.249 330 330 D MsensorDaemon:
09-16 21:53:28.249 330 330 D MsensorDaemon: msensor demon start process detect demon prop = init.svc.akmd09911
09-16 21:53:28.249 330 330 D MsensorDaemon:
09-16 21:53:28.249 330 330 D MsensorDaemon: start_msensor_demon
09-16 21:53:28.500 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.500 330 330 E MsensorDaemon: [99] ''
09-16 21:53:28.600 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.601 330 330 E MsensorDaemon: [98] ''
09-16 21:53:28.701 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.701 330 330 E MsensorDaemon: [97] ''
.....
09-16 21:53:38.324 330 330 E MsensorDaemon: [01] ''
09-16 21:53:38.424 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:38.424 330 330 E MsensorDaemon: [00] ''
09-16 21:53:38.524 330 330 E MsensorDaemon: start daemon timeout!!
09-16 21:53:38.524 330 330 D MsensorDaemon: msensor demon start akmd09911 fail
09-16 21:53:38.524 330 330 D MsensorDaemon: Msensor deamon2 statr!!!!!!!!!!!!
09-16 21:53:38.525 330 330 D MsensorDaemon: open demon attr err = No such file or directory
-> and after:
09-16 21:53:29.396 448 448 I AKMD2 : AKMD 6D with Pseudo Gyro v20130531(Library for AK9911: v6.1.1.531) started.
09-16 21:53:29.396 448 448 I AKMD2 : Debug: ON
09-16 21:53:29.399 448 448 E AKMD2 : LoadPDC:106 fopen Error (No such file or directory).
Ignore the errors...
If your sensor is not the akm09911, you can find it yourself:
V:\Android\logs>adb shell cat /sys/bus/platform/drivers/msensor/chipinfo
akm09911 Chip
Ok, now open cpu-z or Mtk Engineering (Msensor data) and you will find your compass ready to use (and to calibrate!).
I have ported your all your RR Roms to Wiko Fever 4G fixing many problems, but not all:
- RR-N-v5.8.3-20170527-e481-Official -> VERY stable, compass and gps working, kernel 3.10.65 Stock, FM Radio and front flash NOT working
- RR-N-v5.8.4-20170903-E481-Release.zip -> instable, compass, FM Radio and gps working, kernel 3.10.65 Stock, front flash NOT working
- Resseruction Remix N 5.8.3 By Asfand.zip -> the MOST stable, compass and fm radio working, kernel 3.18.x (MM_V34 Stock), front flash AND gps NOT working. It's a pity that the kernel can not link /dev/stpgps and read /dev/ttyC2 (while it can on 3.10.x kernels!)... I reassembled the boot.img and edited the init.scripts many and many times trying everything... but, it's a no go, at least with the MM Kernel...
Ok, I think I have to open a new thread for the Wiko Fever releases, if you agree!
Click to expand...
Click to collapse
thank you so much , and please help us to fix front flash
Thanks in advance
Bro do you know how to make a volte patch?
--------- beginning of crash
09-17 11:46:21.913 302 302 F libc : CANNOT LINK EXECUTABLE "/system/bin/mtk_agpsd": cannot locate symbol "UCNV_TO_U_CALLBACK_STOP_53" referenced by "/system/bin/mtk_agpsd"...
09-17 11:46:21.913 302 302 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 302 (mtk_agpsd)
09-17 11:46:21.975 336 336 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-17 11:46:21.975 336 336 F DEBUG : LineageOS Version: '14.1-20170527-OFFICIAL-E481'
09-17 11:46:21.975 336 336 F DEBUG : Build fingerprint: 'Micromax/lineage_E481/E481:7.1.2/N2G47O/29cf694e04:userdebug/test-keys'
09-17 11:46:21.975 336 336 F DEBUG : Revision: '0'
09-17 11:46:21.975 336 336 F DEBUG : ABI: 'arm'
09-17 11:46:21.975 336 336 F DEBUG : pid: 302, tid: 302, name: mtk_agpsd >>> /system/bin/mtk_agpsd <<<
09-17 11:46:21.975 336 336 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
09-17 11:46:21.975 336 336 F DEBUG : r0 00000000 r1 0000012e r2 00000006 r3 00000008
09-17 11:46:21.975 336 336 F DEBUG : r4 f72e158c r5 00000006 r6 f72e1534 r7 0000010c
09-17 11:46:21.975 336 336 F DEBUG : r8 ff8502c8 r9 00000003 sl ff850300 fp f726f010
09-17 11:46:21.975 336 336 F DEBUG : ip 00000000 sp ff850260 lr f72c16a7 pc f72c209c cpsr 200f0010
09-17 11:46:22.197 336 336 F DEBUG :
09-17 11:46:22.197 336 336 F DEBUG : backtrace:
09-17 11:46:22.198 336 336 F DEBUG : #00 pc 0004609c /system/bin/linker (__dl_tgkill+12)
09-17 11:46:22.198 336 336 F DEBUG : #01 pc 000456a3 /system/bin/linker (__dl_pthread_kill+34)
09-17 11:46:22.198 336 336 F DEBUG : #02 pc 0003ded9 /system/bin/linker (__dl_raise+10)
09-17 11:46:22.198 336 336 F DEBUG : #03 pc 0003cb11 /system/bin/linker (__dl___libc_android_abort+34)
09-17 11:46:22.198 336 336 F DEBUG : #04 pc 0003bb14 /system/bin/linker (__dl_abort+4)
09-17 11:46:22.198 336 336 F DEBUG : #05 pc 0003da47 /system/bin/linker (__dl___libc_fatal+22)
09-17 11:46:22.198 336 336 F DEBUG : #06 pc 00009c43 /system/bin/linker (__dl__ZL29__linker_init_post_relocationR19KernelArgumentBlockj+3146)
09-17 11:46:22.198 336 336 F DEBUG : #07 pc 00008f63 /system/bin/linker (__dl___linker_init+358)
09-17 11:46:22.198 336 336 F DEBUG : #08 pc 000027c0 /system/bin/linker (_start+4)
Bro i got this
please help me
@sun75
Bravo! Have you opened the new thread for the Wiko Fever yet?
In other news, I have started work on a custom kernel based on the Wiko Fever MM source. I don't have much time to work on it though, so if anyone would like to help you can submit pull requests to the source here.
..
sun75 said:
I fixed LTE in build.prop, but I don't know how to to do a VoLTE patch: I'm not a developer, but a system engineer!
---------- Post added at 11:10 ---------- Previous post was at 10:56 ----------
I have already seen it:
just unpack the boot.img and edit the init.mt6735.rc. Diff format:
--- Line 21:
on init
+ export LD_SHIM_LIBS "/system/lib/libui.so|libshim_ui.so:/system/lib64/libui.so|libshim_ui.so:/system/lib/libgui.so|libshim_gui.so:/system/lib64/libgui.so|libshim_gui.so"
export USBOTG_STORAGE /storage/usbotg
mount tmpfs tmpfs /mnt/media_rw/ mode=0755,uid=1000,gid=1000
mkdir /mnt/media_rw/usbotg 0700 media_rw media_rw
mkdir /storage/usbotg 0700 root root
mount tmpfs tmpfs /storage/usbotg mode=0755,uid=1000,gid=1000
chmod 0666 /dev/kmsg
export USBOTG_STORAGE /storage/usbotg
-----
The export LD_ is ONE LINE!!
And:
---- Line 1286:
# GPS
service agpsd /system/bin/mtk_agpsd
class main
socket agpsd stream 660 gps system
socket agpsd2 stream 660 gps inet
socket agpsd3 stream 660 gps inet
user gps
group gps radio inet sdcard_r sdcard_rw misc
+ setenv LD_SHIM_LIBS "/system/bin/mtk_agpsd|libshim_agps.so"
service wifi2agps /system/bin/wifi2agps
--------
Repack the boot.img and reflash it with sp flash tool!
You have to make sure to have /system/[lib|lib64]/libshim_[agps|gui|ui].so
If you open with an hex editor libshim_agps.so you will find the symbol it'll search for!
---------- Post added at 11:37 ---------- Previous post was at 11:10 ----------
I'll open a Wiko Fever thread today, starting with this release: RR-N-v5.8.3-20170527-e481-Official -> RR-N-v5.8.3-20170527-l5460-Official.
Now I'm working on Stock Kernels only (they work on Stock images, they have to work on custom images... and, by the way, the 3.10.x custom based RR is working with the V39 Stock Kernel...): I miss the point on working with custom Kernels, the hardware is the same, what changes is only the OS layer. Please let me know your point of view, maybe in the Wiko thread, once opened. Thank you!
Click to expand...
Click to collapse
The main reasons for working on a custom kernel are:
To have a more up-to-date kernel (so with extra security and bug fixes)
To remove some unnecessary pre-installed bits making it smaller and therefore faster
Adding more tweaking options, such as custom governors, I/O schedulers, TCP congestion algorithms etc.
Add extra features, such as DT2W and Volte (looking at other android kernel sources helps with this)
Other tweaks and fixed if they come up and are needed
Besides, I'm a developer, and not a systems engineer
..
Thread Updated added TWRP 3.0.0 ported by Rick02
CrDROID and hexagon rom is on development
Hit the thank button
Gratitude
Really thankful to you man! Hats off:victory:
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
Hope my heat issue resolves
Hello,
the Rom works fine and smoothly on my Wiko Fever 4g. The compass, front flash, UKW-Radio and Sim-Contacts are not working but I have restore the Contacts from Google.
When the display is on, it pulls up to 1.7 amps from the battery. I hope that there will be updates with bug fixes and security patches soon.
Otherwise good work.
NobodyDbg said:
Hello,
the Rom works fine and smoothly on my Wiko Fever 4g. The compass, front flash, UKW-Radio and Sim-Contacts are not working but I have restore the Contacts from Google.
When the display is on, it pulls up to 1.7 amps from the battery. I hope that there will be updates with bug fixes and security patches soon.
Otherwise good work.
Click to expand...
Click to collapse
i dont have wiko fever i only support mmx
sun75 will help you
Thanking
I would like to thanks XDA team . I have been waiting for months just for a single update for. MMX canvas 5 . Now this morning I found noighat for my phone . Thank you very much XDA team. Keep it on .
Rahul1436 said:
I would like to thanks XDA team . I have been waiting for months just for a single update for. MMX canvas 5 . Now this morning I found noighat for my phone . Thank you very much XDA team. Keep it on .
Click to expand...
Click to collapse
Thanks goes to Arshjot Singh
Hit the thanks button
Bug in Video playback
Harishwarrior said:
{
"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"
}
Lineage 14.1
Arshjot singh made an another rom for Micromax Canvas 5.He puts his time ,Skills ,Effort and Brain on the line to make this awesome Rom.
Without wasting any further time. Lets get started.:fingers-crossed:
Requirements:
You must be in stock lollipop rom , whether it's Rooted or Non rooted
How to install :
1. Download and copy the Rom to your SD card.
2. Backup your Rom using TWRP recovery.
3. Format data and Wipe Factory reset your Phone.
4. Flash the Rom.
5. Change the language.
6. Go to developer option, and set the Animation to 0.5
7. Google apps are not included due to some reason. Go the Google apps link,and select ARM 64 as platform , 7.1 as android,pico as variant.download and flash the zip.
8. Dont install Google system webview otherwise your app will crash
Links:
Lineage 14.1 : https://drive.google.com/uc?id=0B9ToB3iQjd_-eWhuTU1tcnFod00&export=download
TWRP 2.8.7.0: https://forum.xda-developers.com/an...overy-twrp-2-8-7-0-micromax-canvas-5-t3641576
TWRP 3.0.0: https://forum.xda-developers.com/android/development/twrp-3-0-0-micromax-canvas-5-e481-t3677085
Google Apps : http://opengapps.org/
Bugs:
1. Front flash (Not necessary)the default camera app has Selfie flash option try that.
2.Compass (Useless) google maps works without Compass.
Heat Fix:
ONLY TRY THIS , IF YOU FACING HEATING ISSUE .Download and Open kernel Aduitor (Grant root permission)and Go to cpu , select apply on boot , Change the maximum frequency to 1040 Mhz .This will reduces the heat.
CREDITS::angel:
Thanks to
Arshjot singh for Lineage
Infinite4evr for TWRP 2.8.7.0
Rick02::fingers-crossed: for TWRP 3.0.0
Harishwarrior(Me) Moderator.
If you have any ideas or bug fix , Post it down.
This post will be updated Daily or Weekly.Stay tuned
Hit the thanks button......
Click to expand...
Click to collapse
Hello,
I assume that you have already observed bug in video playback issue with this rom.
Solution provided here is for high quality videos but the same can not work for low quality videos.
Is there any known fix for low quality video & formats like .3gpp ??
QUIZILLA said:
Hello,
I assume that you have already observed bug in video playback issue with this rom.
Solution provided here is for high quality videos but the same can not work for low quality videos.
Is there any known fix for low quality video & formats like .3gpp ??
Click to expand...
Click to collapse
Try SW Decoder or use stock video player(Gallery)
Related
{
"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"
}
Welcome to the Cyanmobile eXperience
Hey there peeps, I compiled a new ROM for the HTC Sapphire -- CyanMobile!
It's made by the CyanMobile team, led by Squadzone.
Here's a short description (according to https://raw.github.com/CyanMobile/android_cyanmobile/gingerbread/Definitions.txt) with grammar edited by me:
What is CyanMobile?
CyanMobile is an aftermarket ROM like CyanogenMod, MIUI, JoyOS, LewaOS and others that are built from source. It is based on CyanogenMod 7 (Gingerbread v2.3.7) and uses modifications from AOSP and AOKP
Thanks To CyanogenMod Team, AOKP Team, and AOSP Team for Their Work
**********************************************************************************************************************
** CyanMobile is Short of " *Cyan* (CyanogenMod) *Mob* (Mobiling) *I* (Improving) and *L* (Let's) *E* (Experiment)" **
**********************************************************************************************************************
All features are based on what uses do and what users need with a lots of improvement here and there.
This ROM optimizes Gingerbread, but uses updates from other branchs (ICS stuff, AOSP and AOKP) with reverse engineering or backporting skill.
It can be used without needing to have any Google application installed....
Let us show you what is in CyanMobile:
====================================================================================================
1. Statusbar :
* Date
- Show/Hide Date
- Date Colour
* Notications
- Ticker Color
- No Title Color
- Latest Title Color
- Ongoing Title Color
- Clear Label Button Color
- Title Color
- Item Color
- Time Color
- Tile View [ Android 4.2 ]
* Icons
- Show/Hide Notification Icons
- Show/Hide Statusbar Icons
- Show/Hide Headset/Alarm/Bluetooth/Gps/Sync/Wifi/3G/4G Icon
* Clock
- 4 Clock styles (Right, Left, Center and Hide)
- Clock Color
- Clock Font Size
* Carrier label
- Show/Hide Carrier Label
- Bottom Carrier Label
- 3 Carrier Label On Statusbar Styles (Right, Left and Center)
- Carrier Label Color
- 4 Carrier Logo Styles (Right, Left, Center and Custom Logo)
* Signal
- 5 Different Styles (Bars, Text, Text w/dBm, text w/Auto Color and Hide)
- Wifi Signal Text
* Battery
- 7 Different Styles (Icon, Percentage, Top Statusbar, Side Bar, Behind Statusbar, Navigation Bar and Hide)
- 3 Different Battery Percentage Format (Default, Percentage and Full Color)
- Statusbar Battery Color
* Power Widget
- 4 Different Layouts (Default, Bottom, Grid and Tab)
- Music Widget
- Grid Layout Customizing
* Misc
- Refactor New Statusbar Layout
- Power Clock
- Power Date
- Weather PopUp
- Shortcut Button
- Show/Hide Statusbar
- Reverse Statusbar Icons And Layout
- Statusbar Brightness Control
- Statusbar Fonts Size
- Statusbar Icons Size
- Statusbar Height Size
- Statusbar Background
- Statusbar Background Color
- Notification Background
- Notification Background Color
====================================================================================================
2. Framework :
* Lockscreen
- 7 Different Lockscreen Styles (Sliding Tab, Rotary, Lense, Ring, Honeycomb (beta), Circular (alpha) , Sense (Beta) , Jellybean Glow (Beta) and Jellybean Pad (BETA) )
- Lockscreen Widget Color
- Sms/Call Notifications
- Fuzzy Clock
- Kanji Clock
- Custom Text Lockscreen
- Widget Layouts
- Pattern Styles
* Power Saver
- Screen Off Data Action
- Data Action Delay
- Sync Action
- Sync Time Interval
- Screen Off Wifi Action
- Sync Data Usage
- Mobile Data Preference
* Application
- Native A2SD Framework Core
- Installation Place
* Display
- Bravia Engine
- Rotation Animation
- Window Animations
- Transition Animations
- LCD Density
* Input
- Quick Key Behavior
- Enable/Disable Vibrate on Shutdown
- Explorer Key
* Power Menu
- Show/Hide Power menu/Silent/Airplane/Profile/Screenshot/Power saver/Hibernate/Suspend Toggles
* Fonts
- Change Fonts System
- Change Fonts Type
* OverScroll
- Effect
- Color
- Weight
* Core Replacer
- Change System Apk
- Change Framework Apk/Jar
* Boot/Shutdown animation and Sound
- Preview
- Change Bootanimation
- Change Shutdownanimation
- Change Bootsound
- Reset
* Misc
- New Notifications Design
- Intruder Alert is Life
- New Dialog Design
- Backported Some Apis From Jellybean
- Clear Market Data
- Global Text Color Change
- Global App Background Change
- Soft Button Statusbar
- Navigation Button Bar
- Choose Navi Button
- Navigation Button Bar Size
- Navigation Bar Background
- Extend Power Menu
- Remap Volume Keys
- Lock Volume Keys
- Volume Key Beeps
- Swap Volume Keys
- Task Switcher
====================================================================================================
3. Sound :
* Features
- Loop Ringtone
- Flip Down To Mute Ringer/Snooze Alarm
- Increasing Ringtone Volume
- Less Frequent Notification Sound
- Battery Full/Low Alert
- Charging Plug/Unplug Sound
====================================================================================================
4. Tethering :
* Features
- Bluetooth Tether
- Auto Usb Tether
====================================================================================================
5. Phone :
* Features
- Smart Phone Call
- Back Button To End Call
- Menu Button To Answer Call
- Reject Call with Message
- Allow Incall UI Touch
- Call Me Louder While Inside Bags
- Speed Dials
- Video As Ringtone
- Ring Delay
- Export/Import SIM Contacts
====================================================================================================
6. Messaging :
* Features
- Bubble/Black/Transparent Theme
- Smart Phone Call
- Hide Avatar
- Strip Unicode
- Emoji Support
- Convo List/Subject Font Size
- Sms Vibrate Morse
- Brutal Sender
- Sms PopUp
====================================================================================================
7. Music :
* Features
- Shake To Next/Prev/Play/Pause/Shuttle Track
- Favorite Folder
- Flip To Play/Pause
- Smooth Play Track
====================================================================================================
8. Locations :
* Features
- Enable/Disable Assisted GPS
- GPS Tracker Performance
- Security Device Finder
====================================================================================================
9. Performance :
* Features
- New I/O Scheduler Option
- New Dithering Support
- Enable Bootsound
- Bootsound Volume
- Enable Shutdownanimation
- Gmaps Hack
- KSM Settings
- Battery Polling
- Low Mem Killer Option
- Scrolling Option
- SD Read Ahead Size option
- Screen Off Max CPU Freq
====================================================================================================
10. Misc :
* Features
- ADWLauncher Improved
- Browser Improved
- Calculator Improved
- FM Radio Improved
- File Manager Updated
- SIM ToolKit Improved
- Screenshots Improved
- Task Manager
- Voice Dialer Improved
====================================================================================================
11. All Binary and Library is up to Date
====================================================================================================
That's it, other features not mentioned here came from CyanogenMod 7
Don't Use Any Scripts Like Link2SD, Bravia Hack, Xloud etc They Are Inbuilt !!
Click to expand...
Click to collapse
To Find OUT the features, YOU NEED TO PLAY AROUND WITH THE ROM xD
CyanMobile tries to improve all hardware functions and is always adding new features so it may have some bugs and requires user feedback to fix the bugs.
DONATION:
Donate to Keyur Maru
Donate to Squadzone
Check Next Post For What's Working ! and What's Not !
=======================
Cyan MoBiLe eXperiance
=======================
What's Working in it ? [ Hope so ]
-Network
-HW
-Audio
-Video
-Cam
-DAMM SMOOTH
-Sensors
What's Not Working ? [ Hope so ]
-You Need to Tell me xD
For Change Log Check Next Post
Change Log for Build #1 [16/01/13]
Initial Release for Sapphire
*****Please Read the Flashing Instructions !*****
Screenshots From Wildfire Buzz , LGE P500 And Galaxy Fit
This are From Other Devices Please Provide me From Sapphire Thank you !
DownLoadS
Current Version
Click to expand...
Click to collapse
update-CyanMobile-eXperience-DS-20130116-Release.zip
Click to expand...
Click to collapse
Click that image to start download of latest rom
Google Apps
Click me to Advance the Exploit [ Google APPS ]
***Important***
How To Flash The Rom xD * IMPORTANT *
-Click Thanks , Rate The Thread And Press Newsworthy Thread ( OPTIONAL BUT * HIGHLY RECOMMENDED * )
-Download The Rom
-Wipe ALL
-Flash The Rom
-Reboot From Recovery
-Now Wait for 3-4 Minutes
-Rom Will Not Boot
-Now Remove Battery
-Reinsert Battery
-Now Start The Phone
-It will Boot up Now
-Enjoy The Rom
Hello,
CMX Users Now I had setted up CMX BuildBot !! Now you could always check status of the builds !!
Keep your eyes here : http://builder.pecancm.insomnia247.nl/job/CyanMobile-Builds/
It is Not Building Only for Sapphire It is Building LG P350 , LG P500 , HTC Buzz and More Devices to be added in future !!
DONATION:
Donate to Keyur Maru For Buying this Phone So I can Provide Further Updates
Donate to Sqadzone
I will be ur tester. sound like a good ROM.
could you include some pics or screen capture? thanks for your effort on our magic.
I want to test this rom. But I can't see link of the rom.
It is released
I have a HTC magic 32A device but I could not find rom for it.
hanntbk said:
I have a HTC magic 32A device but I could not find rom for it.
Click to expand...
Click to collapse
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!
blizard80 said:
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!
Click to expand...
Click to collapse
Is official cm7 for 32A or 32B !! it is same as cm7!
Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk
blizard80 said:
Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk
Click to expand...
Click to collapse
What the hell!!!! I compiled with mods to this device config it says it is for dream_sapphire https://github.com/CyanogenMod/android_device_htc_dream_sapphire
so this is not for this device ?
first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.
blizard80 said:
first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.
Click to expand...
Click to collapse
But i can see gingerbread tree here https://github.com/CyanogenMod/android_device_htc_dream_sapphire/tree/gingerbread
I don't know why cm is not releasing gb builds ? please someone test it and tell me results !!
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
If you can flash CM7 you should be able to flash this!
katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
What hboot and/or radio?
I get that error, but updated the hboot and radio et voila!
It works
BTW I installed the hboot and radio from here
PD: I flashed the ROM but it does not boot.
I get many errors.....
D/AndroidRuntime( 145): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 145): Heap size: -Xmx16m
D/AndroidRuntime( 145): CheckJNI is OFF
W/dalvikvm( 145): Exception Ljava/util/regex/PatternSyntaxException; thrown whi
le initializing Landroid/graphics/Rect;
I/dalvikvm( 145): Rejecting re-init on previously-failed class Landroid/graphic
s/Rect; v=0x0
E/dalvikvm( 145): Class lookup Ljava/lang/NoClassDefFoundError; attempted while
exception Ljava/lang/ExceptionInInitializerError; pending
I/dalvikvm( 145): DALVIK THREADS:
I/dalvikvm( 145): (mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
I/dalvikvm( 145): "main" prio=5 tid=1 RUNNABLE
I/dalvikvm( 145): | group="main" sCount=0 dsCount=0 obj=0x40196198 self=0xce4
0
I/dalvikvm( 145): | sysTid=145 nice=0 sched=0/0 cgrp=default handle=-13450024
00
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145):
E/dalvikvm( 145): VM aborting
I/DEBUG ( 79): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 79): Build fingerprint: 'tmobile/opal/sapphire/sapphire:2.2.1/FRG8
3/60505:user/release-keys'
I/DEBUG ( 79): pid: 145, tid: 145 >>> zygote <<<
I/DEBUG ( 79): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG ( 79): r0 fffffec4 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 79): r4 aca9e5c0 r5 0000ce40 r6 aca9e5c0 r7 00000000
I/DEBUG ( 79): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 79): ip aca9e720 sp bef529d0 lr afd19919 pc aca3fb66 cpsr 200
00030
I/DEBUG ( 79): #00 pc 0003fb66 /system/lib/libdvm.so (dvmAbort)
I/DEBUG ( 79): #01 pc 00064a52 /system/lib/libdvm.so
I/DEBUG ( 79): #02 pc 00064cee /system/lib/libdvm.so (dvmFindSyst
emClassNoInit)
I/DEBUG ( 79): #03 pc 00064d06 /system/lib/libdvm.so (dvmFindSyst
emClass)
I/DEBUG ( 79): #04 pc 0003f2ba /system/lib/libdvm.so (dvmThrowCha
inedException)
I/DEBUG ( 79): #05 pc 0003f31c /system/lib/libdvm.so (dvmThrowCha
inedExceptionWithClassMessage)
I/DEBUG ( 79): #06 pc 000628d4 /system/lib/libdvm.so
I/DEBUG ( 79): #07 pc 0006476a /system/lib/libdvm.so (dvmInitClas
s)
I/DEBUG ( 79): #08 pc 00046e2c /system/lib/libdvm.so
I/DEBUG ( 79): #09 pc 000585e8 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #10 pc 0005863a /system/lib/libandroid_runtime.so
(_Z34register_android_graphics_GraphicsP7_JNIEnv)
I/DEBUG ( 79): #11 pc 000357f6 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #12 pc 0003582c /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 79): #13 pc 000358f6 /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime5startEPKcb)
I/DEBUG ( 79): #14 pc 00008ca2 /system/bin/app_process
I/DEBUG ( 79): #15 pc 000153e0 /system/lib/libc.so (__libc_init)
I/DEBUG ( 79):
I/DEBUG ( 79): code around pc:
I/DEBUG ( 79): aca3fb44 2006447a ecc8f7d1 20004c09 edf0f7d1
I/DEBUG ( 79): aca3fb54 447c4808 6bdb5823 d0002b00 49064798
I/DEBUG ( 79): aca3fb64 700a2226 ee5cf7d1 000435c5 00045183
I/DEBUG ( 79): aca3fb74 0005ea66 fffffec4 deadd00d b510b40e
I/DEBUG ( 79): aca3fb84 4c0a4b09 b083447b aa05591b ca026b5b
I/DEBUG ( 79):
I/DEBUG ( 79): code around lr:
I/DEBUG ( 79): afd198f8 447b4a0d 589cb083 90012600 686768a5
I/DEBUG ( 79): afd19908 220ce008 2b005eab 1c28d003 47889901
I/DEBUG ( 79): afd19918 35544306 d5f43f01 2c006824 b003d1ee
I/DEBUG ( 79): afd19928 bdf01c30 00028c26 ffffff88 1c0fb5f0
I/DEBUG ( 79): afd19938 b0871c3d a9044355 1c16ac01 604d9004
I/DEBUG ( 79):
I/DEBUG ( 79): stack:
I/DEBUG ( 79): bef52990 00000000
I/DEBUG ( 79): bef52994 00000000
I/DEBUG ( 79): bef52998 afd4372c
I/DEBUG ( 79): bef5299c afd436d8
I/DEBUG ( 79): bef529a0 00000000
I/DEBUG ( 79): bef529a4 afd19919 /system/lib/libc.so
I/DEBUG ( 79): bef529a8 00000000
I/DEBUG ( 79): bef529ac afd18985 /system/lib/libc.so
I/DEBUG ( 79): bef529b0 00000000
I/DEBUG ( 79): bef529b4 0005ea66
I/DEBUG ( 79): bef529b8 0000ce40
I/DEBUG ( 79): bef529bc aca9e5c0
I/DEBUG ( 79): bef529c0 00000000
I/DEBUG ( 79): bef529c4 afd189e3 /system/lib/libc.so
I/DEBUG ( 79): bef529c8 df002777
I/DEBUG ( 79): bef529cc e3a070ad
I/DEBUG ( 79): #00 bef529d0 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529d4 aca64a57 /system/lib/libdvm.so
I/DEBUG ( 79): #01 bef529d8 41d1dd8d
I/DEBUG ( 79): bef529dc 41d5b7db
I/DEBUG ( 79): bef529e0 00080f40
I/DEBUG ( 79): bef529e4 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529e8 000001b4
I/DEBUG ( 79): bef529ec 00000000
I/DEBUG ( 79): bef529f0 00000000
I/DEBUG ( 79): bef529f4 00000000
I/DEBUG ( 79): bef529f8 00000000
I/DEBUG ( 79): bef529fc aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef52a00 00080f40
I/DEBUG ( 79): bef52a04 00000000
I/DEBUG ( 79): bef52a08 0000ce40
I/DEBUG ( 79): bef52a0c aca64cf3 /system/lib/libdvm.so
I/ServiceManager( 76): service 'media.camera' died
I/ServiceManager( 76): service 'media.audio_policy' died
I/ServiceManager( 76): service 'media.audio_flinger' died
I/ServiceManager( 76): service 'media.player' died
I/Netd ( 147): Netd 1.0 starting
I/ ( 146): ServiceManager: 0xad50
I/HTC Acoustic( 146): libhtc_acoustic.so version 1.0.1.1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara_VODA-Spain.csv -1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara4.csv -1.
E/HTC Acoustic( 146): read audio para from file failed -1
E/AudioHardwareMSM72XX( 146): Could not set acoustic parameters to share memory
: -1
D/AudioHardwareMSM72XX( 146): mNumSndEndpoints = 13
D/AudioHardwareMSM72XX( 146): BT MATCH HANDSET
D/AudioHardwareMSM72XX( 146): BT MATCH SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH BT
D/AudioHardwareMSM72XX( 146): BT MATCH CARKIT
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_FULL
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_VCO
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_HCO
D/AudioHardwareMSM72XX( 146): BT MATCH NO_MIC_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH FM_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET_AND_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH FM_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH CURRENT
D/AudioHardwareInterface( 146): setMode(NORMAL)
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> very important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
pirlano said:
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> i don't think it's too much important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
Click to expand...
Click to collapse
grep is your friend
MCTL_COMPID_ACTUATOR
Zarboz said:
grep is your friend
MCTL_COMPID_ACTUATOR
Click to expand...
Click to collapse
i know, the problem is in liboemcamera.so, mctl_init & sensor_init are changed, and i'm looking at this
i was just asking if One XL devs already solved this problem in the past or not, or if you have some hints
In One S liboemcamera there is one only "MCTL_COMPID_ACTUATOR handle is NULL" reference:
.rodata:000BBAEA aMctl_compid__0 DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
In One liboemcamera there are three reference:
.rodata:000AAB54 aMctl_compid_ac DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0 ; DATA XREF: sub_1F240+A64o
.rodata:000C650C aSMctl_compid_0 DCB "%s MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
.rodata:000C7EF4 aSMctl_compid_2 DCB "%s: MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
the one causing the error is the first
in dmesg, error happens beetween this two lines:
<6>[ 141.009064] c1 4731 [CAM] mt9v113_ioctl, cfgtype = 10
(reached with original cam and zoe mod)
it's in drivers/media/video/msm/sensor/mt9v113_v4l2.c
function: int mt9v113_sensor_config(void __user *argp)
<6>[ 141.009430] c1 4731 [CAM] vfe32_proc_general: cmdID = START
(start is not reached with Zoe mod)
it's in drivers/media/video/msm/vfe/msm_vfe32.c
function: static int vfe32_proc_general(
struct msm_cam_media_controller *pmctl,
struct msm_isp_cmd *cmd,
struct vfe32_ctrl_type *vfe32_ctrl)
Will be great to be ported this feature and new [ROM] MaximusHD 10.0.0 - 4.2.2 Sense 5 -> will be the best one for ONE S
Will wait this with big impatience to be fixed and work of my favorite phone - One S
Thanks
i'm using this tutorials to try to debug liboemcamera.so:
http://forum.xda-developers.com/showthread.php?t=2050393
http://forum.xda-developers.com/showthread.php?t=1374345
but i'm currently stuck here:
http://forum.xda-developers.com/showpost.php?p=45827106&postcount=13
EDIT: solved few problem
but now, i'm stuck, again
ptrace: I/O error.
If someone want to try to debug native android library using IDA Pro...
[console 1] -> one time only
adb push the gdbserver from ndk to data/local/tmp
adb shell su
adb chmod 755 gdbserver
[console 2] -> don't forget it or debug client will not connect!
adb forward tcp:1111 tcp:1111
[console 3] -> start binary you want to debug (or binary that load library that you want to debug liboemcamera.so in my case, using mm-qcamera-app) -> leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (this is to disable ASLR, that cause library to be loaded at random address)
cd system/bin
./mm-qcamera-app
1 or 2
[console 4]->leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (just to be sure)
ps (look at PID of mm-qcamera-app)
cd data/local/tmp
./gdbserver --attach :1111 PID_NUMBER_of_mm-qcamera-app
[console 5]
(adb pull system/lib and system/bin here->C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin)
(start gdb from ndk from command line)
gdb.exe
(gdb) set height 0
(gdb) set solib-search-path ./
(gdb) directory C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin
(gdb) target remote 127.0.0.1:1111
Remote debugging using 127.0.0.1:1111
0x4005fe48 in ?? ()
(gdb) info sharedlibrary
Reading symbols from C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/preb
uilt/windows-x86_64/bin/mm-qcamera-app...done.
WARNING: no debugging symbols found in C:/android-ndk-r9/toolchains/arm-linux-an
droideabi-4.6/prebuilt/windows-x86_64/bin/mm-qcamera-app.
Either the binary was compiled without debugging information
or the debugging information was removed (e.g., with strip or strip -g).
Debugger capabilities will be very limited.
For further information: http://wiki/Main/GdbFaq#No_debugging_symbols_found
From To Syms Read Shared Object Library
0x40003240 0x4000b978 No C:/android-ndk-r9/toolchains/arm-linux-andro
ideabi-4.6/prebuilt/windows-x86_64/bin/system/bin/linker
0x40055940 0x40085d0c No libc.so
0x400a07f4 0x400a0998 No libstdc++.so
0x400a4e80 0x400b5164 No libm.so
0x40044180 0x40045d44 No liblog.so
0x40027a18 0x4003059c No libcutils.so
0x4025f6a0 0x40263008 No libgemini.so
0x4022f578 0x402543cc No libmmjpeg.so
0x400ca8b0 0x40161250 No liboemcamera.so
0x40296638 0x40296b50 No libmmstillomx.so
0x402a1494 0x402a1630 No libimage-omx-common.so
0x4029a658 0x4029e414 No libimage-jpeg-enc-omx-comp.so
0x4028a284 0x40291a5c No libmmcamera_interface2.so
(gdb)
NOW you have information about library base address! Nice! Copy and paste these information
Now you can just use CTRL+C on console 4, and execute instruction for console 4 again, so we can debug using IDA this time
(IDA)
for new versions->Debugger, Debugger option, option, uncheck "Use hardware temporary breakpoints"
Debugger,Switch Debugger,Remote GDB debugger and check Set as default debugger
Debugger, Process option, applicazion path (../system/bin/blabla), input file (same or ../system/lib/libblabla.so if debugging lib), Hostname: localhost, Port 1111 (or select youself, you will need to use it for all commands) and check "Set as default network setting"
Now load the file you want to debug
File->Open->liboemcamera.so in my case->Ok/Load->Check "Manual load" from the popup->OK->Input 0:400ca8b0 in my case (base address)->Load all section or section that you need->Yes
Wait for autoanalysis, and do some static analysis by yourself, set some breakpoint, etc,etc
When you are ready to debug: Debugger,Start process, Yes
TADA! The ****ing IDA+gdb should now be able to do step by step debug, but i got a ****ing ptrace: I/O error.
using HTC One Mini libs + updating kernel camera parts from HTC One Mini source, front camera is working good, but rear camera quality is really really bad, need a fix
i'll post an alpha mod soon
zoom bug (green rectangle on jpeg) is still present
EDIT: quality became bad because of wrong Auto White Balance not working good with M4 libs, so with a clean installation it will still working good, but if you came from Zoe fix from Magio, you will need to go back to stock libs/camera apps or do a fresh installation
zoe is working but need camera.apk modding to force it (it should be easy, since apk can be decompiled almost to source code)
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
pirlano said:
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
Click to expand...
Click to collapse
Well this work over your old kernel to make the one xl roms boot
Sent from my HTC One S using Tapatalk 2
yes, camera part only is changed, tomorrow i'll work on camera.apk
pirlano said:
yes, camera part only is changed, tomorrow i'll work on camera.apk
Click to expand...
Click to collapse
Ok cool need any help send me a pm
Sent from my HTC One S using Tapatalk 2
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
razlack said:
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
the question is not "when", but, "if"
i'll start lessons next week, so i will be unable to continue
EDIT:
today, instead of looking at m4 camera.apk, i tryed to fix ffc with stock kernel and m7 libs, i think i have found the solution, don't know if it will work, but it's the better idea that i have found until now
EDIT2:
mt9v113 seems to be incompatible with m7 libs, cannot found a solution, we need an experienced arm hacker or hex-rays arm decompiler (if someone use it at work, license is too expensive for home users)
an ather way it's to create a mt9v113_act.c driver, but i think i'm not able to do that, and if it will work, but maybe a dummy one will work too, will try when i have time
for now the only way it's to use m4 libs, so camera.apk needs hacking (this is much more easy), i will try tomorrow
I'm also trying to understand what's causing the zoom bug...
also with both m4 and m7 libs (with kernel patches to make camera working) manual touch autofocus seems to be buggy with slow motion mode and with 60fps mode
and camera auto white balance need a fix, i'm starting to think that it's better to mod our stock camera, without zoe...****ing close source libs...
CameraNext crashes on most ROMs I install. I am currently on a stock rom and still crashing. Normally I would just use another camera app but if it's fixable - awesome. Google Camera works fine.
I have attached 2 crash reports. I cannot generate the second one again, which it a bit odd.
Is there a fix? TIA
Kind regards
Benjamin
Android:
12.0 YNG1TAS17L
5.0.2
Camera
CameraNext
2.0.004
Crash 1
java.lang.RuntimeException: Media server died.
at com.android.camera.Y.onError(SourceFile:33)
at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1195)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Crash 2
Build fingerprint: 'oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 10164, tid: 10181, name: Binder_2 >>> com.cyngn.cameranext <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 00000000 r1 ad32209c r2 00000025 r3 00000000
r4 a3018040 r5 b6ba5de1 r6 ad320080 r7 00002000
r8 adde7b54 r9 00000000 sl 00002000 fp adde7bf0
ip b6bb5ec0 sp adde7b38 lr b6ba5ea5 pc b6e261f8 cpsr a0000030
backtrace:
#00 pc 000981f8 /system/lib/libandroid_runtime.so (JNICameraContext::copyAndPost(_JNIEnv*, android::sp<android::IMemory> const&, int)+35)
#01 pc 00098353 /system/lib/libandroid_runtime.so (JNICameraContext:ostData(int, android::sp<android::IMemory> const&, camera_frame_metadata*)+102)
#02 pc 0001e995 /system/lib/libcamera_client.so (android::Camera::dataCallback(int, android::sp<android::IMemory> const&, camera_frame_metadata*)+54)
#03 pc 00022321 /system/lib/libcamera_client.so (android::BnCameraClient:nTransact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+220)
#04 pc 00017fc5 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+60)
#05 pc 0001cf7b /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+582)
#06 pc 0001d09f /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+38)
#07 pc 0001d0e1 /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
#08 pc 0002124b /system/lib/libbinder.so
#09 pc 0000ef11 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+112)
#10 pc 0005a62d /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+72)
#11 pc 0000ea81 /system/lib/libutils.so
#12 pc 00013a1b /system/lib/libc.so (__pthread_start(void*)+30)
#13 pc 00011a0f /system/lib/libc.so (__start_thread+6)
* Cleared Data and Cache, no bacon.
I hit this bug constantly. For me, the camera is effectively unusable. I've also tried clearing cache &c.
My cameras have stopped too & I don't know how to remove or try better camera software pkg. If someone could help me to do this it would be great. Thankyou Currently running 1+1,
Resurrection Remix, 5.5.6 with slim0 gapps,+ latest cm12.1 nightly Don't have ear speaker on phone calls working either but I need my cameras back first.
wel for best results flash the K1 Color Os package in recovery.
amazing.
also you could install the A Better Camera app, its equally good if you know how to play with the light.
lastly, the Moto V3 camera port is superb..
u need to try all three to know which works best for u.
regards
---------- Post added at 01:38 PM ---------- Previous post was at 12:43 PM ----------
here are the links for the cams I use which are tested working on OP1 and LG G2 and Nexus 5.
superb apps..
COS Cam Port - http://d-h.st/gskk
here is the original thread of the port - http://forum.xda-developers.com/oneplus-one/themes-apps/coloros-camera-port-t3034148
Moto Cam port - http://d-h.st/SF8S
(remove - http://d-h.st/Prw9)
here is the original thread of the port - http://forum.xda-developers.com/android/apps-games/flashable-port-moto-camera-fullfilled-t3172783
all credits to the original devs, i am just sharing....
regards
My Unoffical Resurrection Remix (PIE)
(LuisROM) for Samsung Galaxy S5 (klte)
{
"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:
*** Disclamer
/*
* 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.
*
*/
EOL - End of life / End of development since 2020-02-13! The RR Team has stopped the development. Please switch to my LuisROM based on crDroid.
Link crDroid builds: http://luis-builds.de/downloads/lineageos/cr/
This is my unofficial Resurrection Remix V7.x (pie) cutsom rom.
This is a ROM that works on Samsung Galaxy S5 (klte/snapdragon/G900F) only! This ROM comes with a highly-customized kernel, as well as some other very custom modifications.
I will NOT provide support if you install a custom kernel!
Changelogs: http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/RR-P-Changelog.mkdn
Introduction
Hello Friends!
I had troubles to find current builds for my devices so I decided to make regular builds for my devices. When my friends told me about similar problems, I extended the builds to include their devices as well. So these builds were and are mainly for my friends and me, but I finally decided to provide them also for public download.
My ROMs
My unofficial Resurrection Remix (LuisROM) an awesome combination of performance, customization, power and the most new features, brought directly to your device. The LuisROM build server generates automaticly every 2nd days new builds directly from the sources.
Notice
Sometimes I get a lot of help or feature requests from users of my LuisROMs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs . Please understand if I can not always answer directly.
ROM features:
Based off latest Resurrection Remix V7.x (pie), lineageos and aosp sources
Latest security patches
OTA Updater (LineageOS Updater) since builds from 2019-01-26
Compatible with EX Kernel Manager
Many other misc. performance and stability improvements under the hood
Kernel: Linux 3.4.x Kernel with many mods other devs and me (thanks for your incredible work!)
Removed lots of excessive bloat (improves security and performance)
Improved stability (several bugs not listed here have been fixed)
More I/O-Schedulers
Optimized for performance and battery life
Compatible with systemless root
Many other misc. improvements not listed here
Installation instructions:
First time installation:
Unlock your bootloader
Flash recovery zip (TWRP)
Reboot into TWRP Recovery
Wipe all data
Flash my lastest RR LuisROM (download here)
Optional: Flash Open GApps and Magisk
Reboot and enjoy
OTA App update installation (auto):
Go to Settings > Advanced > Updater
Press reload button (right corner)
Select download on the new build list
After download select update/flash new build (the update process can take longer than expected on treble devices!)
Reboot and enjoy
Download
Samsung Galaxy S5 builds: (http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/)
My other devices/ROMs: (http://luis-builds.de/downloads/lineageos/)
Download OpenGapps: (http://opengapps.org)
Flash latest TWRP: (download here)
Changelog
Developer: http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/RR-P-Changelog.mkdn
Telegram group:
https://t.me/rr_luisrom
Thanks To/Credits
Special thanks to Teams:
LineageOS team: https://www.lineageos.org
RR Team: https://www.resurrectionremix.com
OMNI team https://omnirom.org/about/
SLIMROMS https://slimroms.org/#/about
topjohnwu (Magisk) https://forum.xda-developers.com/apps/magisk
Thanks to the best devs on earth:
francokernel (https://forum.xda-developers.com/member.php?u=3292224)
sultanxda (https://forum.xda-developers.com/member.php?u=4800121)
flar2 (https://forum.xda-developers.com/member.php?u=4684315)
nathanchance (https://forum.xda-developers.com/member.php?u=6842057)
eng.stk (https://forum.xda-developers.com/member.php?u=3873953)
zx2c4 for the wireguard vpn ROM Integration (https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635)
and of course to all the supporters.
Thanks for the Sources/Blobs/Tweaks
Resurrection Remix (https://github.com/LineageOS)
ArrowOS (https://github.com/ArrowOS-Devices)
TheMuppets (https://github.com/TheMuppets)
My Sources/Blobs/Tweaks
FraEgg (me) (https://github.com/FraEgg)
XDA:DevDB Information
[ROM][EOL][KLTE][PIE]Unofficial Resurrection Remix [V7.x][LuisROM][G900F], ROM for the Samsung Galaxy S5
Contributors
8224Freak
Source Code: https://github.com/FraEgg
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: RR, LineageOS, Resurrection Remix, AOSP
Version Information
Status: Stable
Stable Release Date: 2019-03-18
Created 2019-03-18
Last Updated 2020-02-15
Reserved
Hello,
Is substratum working in that ROM?
I want to apply overlays but nothing happens after applying..
Regards
Sent from my SM-G960F with Tapatalk
How many resurrection-remix are their, and what the different between both
support Samsung S5 SM-G900W8 ?
Latest build is not working for me.
It stucks at Samsung Galaxy S5 logo and then reboots to download mode..
Regards
Sent from my SM-G960F with Tapatalk
Just installed on never rooted 900F
Root - reboot - TWRP - reboot - Wipe system, Data, Davlik, Cache. flash ROM + Gapps - Reboot and everything is working very nice No single lock up or reboot etc.. in this few hours of adjusting..
ps. Nice ring tone
I use it for 3~ days and the rom worked almost perfectly , with the exception after 3 days it just restarted and stuck in boot , i dont know what to do , i tryed multiple bootloader/modem and now i am with BL_G900FXXU1BNL9 and CP_G900FXXU1BNL9 , is a way i can see the original bootloader/modem also a log file ?
@sunny_sall
As written right in the beginning of #1:
ONLY for G900F
bmwdroid said:
@sunny_sall
As written right in the beginning of #1:
ONLY for G900F
Click to expand...
Click to collapse
Exactly , my model is g900F . i will try to give you guys more info in a bit , i am trying to get it rooted and take a logcat
Edit : https://ufile.io/0fmwx if u want me to upload somewhere else just specify because the atachement has 50 kb more over the limit and xda does't allow it , i made a clean instal with the latest update , how should i repost the log when the phone goes to boot and stuck there if the android does't work ?
Model of the phone with droid hardware info :
Code:
DEVICE
Model: SM-G900F (rr_klte)
Manufacturer: samsung
Baseband Version: G900FXXU1BNL9
RIL Version: Samsung RIL v3.0
Build Number: rr_klte-userdebug 9 PQ2A.190305.002 eng.franke.20190401.105640 test-keys
Build Fingerprint: samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys
Bootloader: G900FXXU1BNL9
Java VM: ART 2.1.0
OS Version: P (9)
SDK: 28
DISPLAY
Resolution: Full HD, 1080x1920 pixels
Software Density: 480 dpi (xxhdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 1 (v7l)
Board: MSM8974
Chipset: Qualcomm MSM8974PRO-AC
Cores: 4
Clock Speed: 268 MHz - 2457 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32
CPU Governor: interactive
Kernel Version: 3.4.113-LuisROM-sp-g45c2f4a178e
Kernel Architecture: armv7l
GRAPHICS
Renderer: Adreno (TM) 330
Vendor: Qualcomm
OpenGL Version: OpenGL ES 3.0
RAM
Total: 1701 MB
Java Heap: 192 MB
STORAGE
Internal: 11.5 GB
EXTERNAL: Not Detected
PRIMARY CAMERA
Resolution: 15,9 MP
Flash: Yes
Video Resolution: 4K UHD, 3840x2160
Supported Resolutions:
Image:
5312x2988
3984x2988
3264x2448
3264x1836
2560x1920
2048x1152
1920x1080
1280x960
1280x720
800x480
640x480
320x240
Video:
3840x2160 (4K UHD)
1920x1080 (Full HD)
1440x1080
1280x720 (HD)
800x450
800x480 (WVGA)
720x480
640x480 (VGA)
352x288
320x240
176x144
SECONDARY CAMERA
Resolution: 2,1 MP
Video Resolution: 4K UHD, 3840x2160
Supported Resolutions:
Image:
1920x1080
1440x1080
1280x960
1280x720
960x720
720x480
640x480
320x240
Video:
3840x2160 (4K UHD)
1920x1080 (Full HD)
1440x1080
1280x720 (HD)
960x720
800x450
720x480
640x480 (VGA)
352x288
320x240
176x144
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: Yes
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
MPU6500 Acceleration Sensor
MPU6500 Gyroscope Sensor
MPU6500 Uncalibrated Gyroscope Sensor
AK09911C Magnetic field Sensor
AK09911C Magnetic Sensor UnCalibrated
Barometer Sensor
TMG399X Proximity Sensor
TMG399X RGB Sensor
MPL Rotation Vector
MPL Game Rotation Vector
SAMSUNG Step Detector Sensor
SAMSUNG Step Counter Sensor
SAMSUNG Significant Motion Sensor
HRM Sensor
HeartRate Sensor
MAX86900
Corrected Gyroscope Sensor
Game Rotation Vector Sensor
Gyroscope Bias (debug)
GeoMag Rotation Vector Sensor
Gravity Sensor
Linear Acceleration Sensor
Rotation Vector Sensor
Orientation Sensor
Created by Droid Info
Made a clean install of the 20190401 version on my G900F with TWRP 3.2.3-0 yesterday with pico gapps and Magisk.
Installation went well, booted quite fast.
Installed 22 Apps.
Only problem is that the screen shots off as soon as I take my finger away.
Shutdown time is set to 2'.
I love RR ROMs and am quite sad that it doesn't work on my S5.
Sent from my v1awifi using XDA Labs
Sometimes when I want to unlock the smartphone, I'm only half a blue screen with clock displayed. The device can then no longer be spun. what can you do to fix this problem?
Is there a way so i can make use the heart rate sensor in this rom?
Hey 8224Freak, there is a bootloop when dirty flashing 7.0.2 (RR-P-v7.0.2-20190422-klte-Unofficial-LuisROM.zip) over an existing 7.0.1 install. I did not have time to try a clean flash, but I did grab some logs using this boot debug patcher
Code:
************ Failure starting system services
04-23 18:24:35.311 2041 2041 E System : java.lang.SecurityException: Permission android.permission.WRITE_MEDIA_STORAGE is not a changeable permission type
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:383)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.PackageManagerService$PackageManagerInternalImpl.grantRuntimePermission(PackageManagerService.java:24286)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1374)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1269)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissionExceptions(DefaultPermissionGrantPolicy.java:1458)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissions(DefaultPermissionGrantPolicy.java:269)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21354)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1792)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.run(SystemServer.java:464)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.main(SystemServer.java:309)
04-23 18:24:35.311 2041 2041 E System : at java.lang.reflect.Method.invoke(Native Method)
04-23 18:24:35.311 2041 2041 E System : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
04-23 18:24:35.311 2041 2041 E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
04-23 18:24:35.311 2041 2041 E Zygote : System zygote died with exception
04-23 18:24:35.311 2041 2041 E Zygote : java.lang.SecurityException: Permission android.permission.WRITE_MEDIA_STORAGE is not a changeable permission type
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:383)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.PackageManagerService$PackageManagerInternalImpl.grantRuntimePermission(PackageManagerService.java:24286)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1374)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1269)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissionExceptions(DefaultPermissionGrantPolicy.java:1458)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissions(DefaultPermissionGrantPolicy.java:269)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21354)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1792)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.run(SystemServer.java:464)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.main(SystemServer.java:309)
04-23 18:24:35.311 2041 2041 E Zygote : at java.lang.reflect.Method.invoke(Native Method)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
04-23 18:24:35.311 2041 2041 D AndroidRuntime: Shutting down VM
Edit: If no-one else has this problem, I probably stuffed up with opengapps somehow :/ Will clean flash when I have time.
Also, does Google Assistant work for anyone here? (Not just the 'OK Google' hotword which launches google searches - that works, but the actual 'assistant' feature?) The Google app appears to crash when tapping the 'Updates' button.
I don't like it, it's a boring rom
Anyone else having issues with quick tiles , when set the theme of the tiles to oreo style some of the tiles are not present ?
Poswa said:
I don't like it, it's a boring rom
Click to expand...
Click to collapse
Then I suggest that you build a less boring rom and I will be happy to test it.
You should be grateful that we have someone who volunteers their time and also willing to share their hard work for us to enjoy!
KazuDante said:
Anyone else having issues with quick tiles , when set the theme of the tiles to oreo style some of the tiles are not present ?
Click to expand...
Click to collapse
No problems here mate
pmduper said:
No problems here mate
Click to expand...
Click to collapse
are you sure , i mean did you actually put the quick tiles to the oreo style ? screenshot
DISCLAIMER
Code:
Your warranty is now void (if you still have one).
Read the steps carefully!
I am not responsible for data loss, bricked devices or devices which will need USB soldering!
If you do not know what you're doing, stop here!
[COLOR=rgb(243, 121, 52)][B]Latest Release:[/B][/COLOR] 22/06/2022 22:58
[B]BATTERY PERCENTAGE FIX FOR 22/06/2022 RELEASE (CURRENT BUILD):[/B]
With latest release (22/06/2022), some people's battery percentage is stucked at the same level and is not updating until reboot. Here is the fix for that. No need to wipe data or do something special. This file contains kernel update only. Just flash directly with netOdin/Odin.
[B][COLOR=rgb(184, 49, 47)]GEAR S3 FRONTIER/CLASSIC ONLY!![/COLOR][/B] Installed and tested on a few SM-R760 Frontier and get succeed. SM-R770 Classic is also confirmed.
[B]BUT [COLOR=rgb(184, 49, 47)]Korean and LTE versions are NOT TESTED. THEY USE DIFFERENT KERNEL CONFIGURATION. IT WILL PROBABLY CAUSE HARD BRICK!! USE YOUR OWN RISK![/COLOR]
[COLOR=rgb(243, 121, 52)]BEFORE INSTALLATION[/COLOR][/B]
[LIST]
[*][COLOR=rgb(184, 49, 47)][B][COLOR=rgb(184, 49, 47)]DISABLE REACTIVATION LOCK[/COLOR][/B][/COLOR]
[*][COLOR=rgb(184, 49, 47)][B]Charge your watch to 100%[/B][/COLOR]
[*]Keep your device charging while installing firmware
[*]Have a stable computer with Wifi
[*]Take note your current Tizen firmware version for going back to Tizen
[*]Backup all your data
[*]Keep your watch close to your wireless adapter
[/LIST]
[B][COLOR=rgb(243, 121, 52)]INSTALLATION [/COLOR][/B][URL='https://mega.nz/file/gFRVxb6K#A0c0dnw2TspeLzo-m9jWnuieG1vTPfh2Mq5vbQzz0a0'][B](View Detailed Document Here)[/B][/URL]
[LIST]
[*]Flashing process is the same as flashing combination or Tizen firmware
[*][COLOR=rgb(184, 49, 47)][B]Wireless flashing takes 15~45 minutes.[/B][/COLOR]
[/LIST]
[LIST=1]
[*]Extract downloaded zip file to get tar file
[*]Enter wireless download mode
[*]Switch to AP mode
[*]Connect to watch from your wireless adapter
[*]Select tar file for AP section
[*]Flash
[/LIST]
[COLOR=rgb(184, 49, 47)][B]DO NOT interrupt flashing process!
DO NOT shutdown your computer or allow your computer to sleep!
DO NOT enter recovery before WearOS boots completely![/B][/COLOR]
[B][COLOR=rgb(65, 168, 95)]WHAT IS WORKING[/COLOR][/B]
[LIST]
[*]WearOS functions (Notifications, Play Store, Google Account, Assistant etc)
[*]Always on display
[*]Wifi
[*]Bluetooth
[*]Vibrator
[*]Bezel (works like crown)
[*]Tap to wake
[*]Palm to suspend
[*]Mic
[*]HRM (Hear Rate Monitor - Sensor)
[*]Sensors (Accelometer, Gyroscope, Light)
[*]Audio
[*]TWRP
[/LIST]
[B][COLOR=rgb(184, 49, 47)]KNOWN BUGS[/COLOR][/B]
[LIST]
[*]Poor Battery Life compared to Tizen (Old device, new operation system)
[*]Audio (Low sound level, bad quality)
[*]HFP calls on watch (Bad noises, distorted sound)
[*]Some menus on Settings belongs to Ticwatch (just ignore them)
[*]Offline charging boots device
[*]GPS is not working
[*]NFC is not working
[*]Step Counter is not working
[*]Some green text above SAMSUNG logo while booting
[*]Same green text on Wireless Download Mode. It prevents debug messages (Switching to AP mode etc) [B]but functionality is not effected.[/B]
[*]If device goes to TWRP, just click Reboot -> System.
[*]Selinux is in Permissive mode
[*]ADB Root is active
[*]KNOX will be tripped!!
[/LIST]
[B][COLOR=rgb(243, 121, 52)]RESETTING WATCH OR CONNECTING NEW DEVICE[/COLOR]
[COLOR=rgb(184, 49, 47)]NEVER use WearOS settings menu to reset watch!!! It is not tested and may be brick your device.[/COLOR][/B]
Option 1: Flash WearOS again
Option 2: Boot to TWRP and Wipe Data [COLOR=rgb(184, 49, 47)][B](IMPORTANT! Be sure “Use rm -rf instead of formatting” is selected on TWRP settings. (TWRP Settings -> General Settings)[/B][/COLOR]
[COLOR=rgb(243, 121, 52)][B]GOING BACK TO TIZEN[/B][/COLOR]
[LIST=1]
[*]Find and download your Tizen firmware from internet. (Remember, you took note your firmware version before installation)
[*]If you can not find your firmware you can try [URL='https://mega.nz/file/JYoQ2AgY#rqw2jZm_eJHjmGkKz4lzVProxyE1DpZA20jYYce-2ow']THIS TIZEN FIRMWARE[/URL]. [COLOR=rgb(184, 49, 47)][B](It may has different CSC. Be careful!)[/B][/COLOR]
[*]Flash
[/LIST]
[B][COLOR=rgb(243, 121, 52)]TELEGRAM GROUP
SOURCES[/COLOR][/B]
[URL='https://github.com/parasetam0l']Github (parasetam0l)[/URL] for kernel, device tree and other SMDK - Samsung related files.
[B][COLOR=rgb(243, 121, 52)]THANKS TO[/COLOR][/B]
[URL='https://github.com/TO21Consortium/SGSWPlatform']TO21Consortium[/URL] for beautiful SMDK source
[URL='https://github.com/YariKartoshe4ka/redline_kernel_samsung_j4lte']YariKartoshe4k[/URL] for Exynos 7570 kernel source
[URL='https://github.com/Biktorgj/android_device_samsung_pontesolo/tree/master/libsensors']Biktorgj[/URL] for Gear S and SSP sensor sources
[URL='https://wear.revtechs.me/en/download']OneOS [/URL]for TicWatch WearOS2 system dump
Many other developers I came across with Google search.
[USER=12140719]@trapecija[/USER] For SM-R770 Classic feedback
DEVELOPER NOTES :
Soldering USB and Odin USB mode: Done
Install Combination firmware (COMBINATION-FT30_R760XXU2CQL1): Done
Root Access (Combination firmware is pre rooted): Done
Build Tizen Kernel: Done
Upstream Tizen Kernel to latest (from 3.18.14 to 3.18.140): Done
Enable Android configs and disable some Samsung stuff on kernel: Done
Kernel cmdline patch for booting from mmc: Done
TWRP device tree: Done
Build TWRP: Done
MM (memory management) and FB (framebuffer) patch for IOMMU error: Done
PMIC patch for enabling USB: Done
Created fstab file: Done
Update Android Binder kernel driver: Done
Android Boots with ADB support: Done
USB Charging: Done
Mali T720 GPU Driver Update: Done
Decon Framebuffer: Done
S6E36W2X01 LCD Panel: Done
Compile AOSP9: Done
WearOS2 Port: Done
Broadcom 43102 Wifi and Bluetooth SDIO: Done
Palm to suspend: Done
Audio: Partially Fixed (Low sound level and quality)
HFP (Handsfree Protocol): Partially Fixed (Mic works, speaker distorted sound)
Brightness: Done
Vibration: Done
LSM6DSL Accelometer and Gyroscope Sensor: Done
TSL2584 Light Sensor: Done
PPS960 Heart Rate Sensor: Done
SSP Sensor Hub: Partially
Tap to Wake: Done
Always on display: Done
Bezel: Done
THINGS TO DO:
GPS
NFC
Offline charging
Step Counter
Power Optimizations (power.exynos5)
Audio and HFP (mixer_paths.xml)
SSP Sensor Hub
...
...
...
WearOS 3
Code:
ls -l /dev/disk/by-partlabel
lrwxrwxrwx 1 root root 15 Jan 20 23:11 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jan 20 23:11 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jan 20 23:11 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Jan 20 23:11 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Jan 20 23:11 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jan 20 23:11 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jan 20 23:12 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jan 20 23:11 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jan 20 23:11 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Jan 20 23:11 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Jan 20 23:11 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jan 20 23:11 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Jan 20 23:11 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Jan 20 23:11 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Jan 20 23:11 user -> ../../mmcblk0p13
Code:
(parted) print
print
Model: MMC FJX7AA (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 37.7MB 33.6MB tup
2 37.7MB 46.1MB 8389kB ext4 csa
3 46.1MB 48.2MB 2097kB cpnvcore
4 48.2MB 69.2MB 21.0MB ext2 ramdisk2
5 69.2MB 77.6MB 8389kB ext2 ramdisk1
6 77.6MB 86.0MB 8389kB param
7 86.0MB 89.1MB 3146kB cm
8 89.1MB 106MB 16.8MB boot
9 106MB 123MB 16.8MB recovery
10 123MB 139MB 16.8MB ext4 module
11 139MB 339MB 199MB ext4 csc
12 339MB 504MB 166MB ext4 system-data
13 504MB 2538MB 2033MB ext4 user
14 2538MB 3907MB 1369MB ext4 rootfs
15 3907MB 3907MB 262kB steady
I will use
system-data -> /recovery
csc -> /cache
user -> / (system as root)
rootfs -> /data
UPDATE:
I am using
Code:
SM-R870_samsung-freshbl-freshbl-11-RWD1.210503.001-R870XXU1BUH9-user-release-keys.tar.gz
which is referenced from this post. It is Android 11 based WearOS 3. You can also find this file if you search on the internet. This is not a full firmware. Many files are missing. I think they dumped this from a factory device while it is running or they removed some files intentionally.
but I completed missing files for minimal booting. I also fixed Android's binder driver. Now device is booting to Android with working ADB. I can get logs from logcat. Very good!
Next thing is graphics driver. GW4 firmware does not include a surfaceflinger binary. So I built my own surfaceflinger with some modifications. Solis has Mali T720 MP1. I got this from ADB.
Code:
01-23 02:54:06.980 4377 4377 E mali : file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.2)
01-23 02:54:06.986 4377 4377 E mali : ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
01-23 02:54:06.986 4377 4377 E mali : The DDK was built for 0x720 r1p1 status range [0..15], but none of the GPUs matched:
01-23 02:54:06.989 4377 4377 E mali : file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.2)
01-23 02:54:06.989 4377 4377 W libEGL : eglInitialize(0xf3b010a0) failed (EGL_NOT_INITIALIZED)
01-23 02:54:06.990 4377 4377 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
01-23 02:54:06.990 4377 4377 F RenderEngine: eglQueryStringImplementationANDROID(EGL_VERSION) failed
01-23 02:54:06.991 4377 4377 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4377 (surfaceflinger), pid 4377 (surfaceflinger)
Things to check:
Code:
libGLES_mali.so (This is main driver library with many other files)
Mali T72x Kernel driver
UPDATE:
I fixed USB charging and added ambient capabilities to kernel (which is needed for surfaceflinger and in general android).
So this error is gone:
Code:
capabilities requested but the kernel does not support ambient capabilities
I also updated tizen_arm MALI kernel drivers from r12p0 to arm r29p0. With proper libGLES_mali.so, DDK error is gone.
I tried to use Exynos 7570 hardware composer from several roms. Now I am facing a problem with lcd panel. LCD panel gives this error.
Code:
01-01 00:00:10.094 222 222 E HWComposer: getAttribute: getDisplayAttribute failed for display 0: BadParameter (4)
01-01 00:00:10.094 222 222 E HWComposer: getDisplayConnectionType: getDisplayConnectionType failed for display 0: Unsupported (8)
Because of this problems, I stopped porting WearOS and started building LineageOS from stratch. Before building process, I have to prepare a device tree. This repos are helpful for preparing device tree.
Code:
https://github.com/LineageOS/android_hardware_samsung
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos5
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos7580
https://github.com/LineageOS/android_hardware_samsung_slsi_libbt
https://github.com/LineageOS/android_kernel_samsung_universal7580
https://github.com/LineageOS/android_hardware_samsung_slsi_openmax
https://github.com/TO21Consortium/SGSWPlatform
Nice work, just keep going! Many of us are looking forward to this, perseverance!
I've been following "the other thread" for years. I really like yours and the way you show progress and steps very clearly. I hope you'll succeed!
Great work!
Thank you all for your good wishes. It's been a busy week for me.
UPDATE:
I built hwcomposer and gralloc from stratch. Now android recognizes our display.
Code:
11-14 01:04:46.884 1956 1956 D hwcomposer: using
11-14 01:04:46.884 1956 1956 D hwcomposer: xres = 360 px
11-14 01:04:46.884 1956 1956 D hwcomposer: yres = 360 px
11-14 01:04:46.884 1956 1956 D hwcomposer: width = 33 mm (277.090000 dpi)
11-14 01:04:46.884 1956 1956 D hwcomposer: height = 33 mm (277.090000 dpi)
11-14 01:04:46.884 1956 1956 D hwcomposer: refresh rate = 56 Hz
11-14 01:04:46.884 1956 1956 V DisplayResourceManagerModule: externalMPP type(4), index(0)
11-14 01:04:46.884 1956 1956 I hwcutils: Open /dev/s5p-smem
11-14 01:04:46.885 1956 1956 V DisplayResourceManagerModule: externalMPP type(5), index(0)
11-14 01:04:46.886 1956 1956 I hwcomposer: PSR info devname = /sys/devices/14830000.decon_fb/psr_info
11-14 01:04:46.886 1956 1956 I hwcomposer: PSR mode = 2 (0: video mode, 1: DP PSR mode, 2: MIPI-DSI command mode)
11-14 01:04:46.886 1956 1956 I hwcomposer: Panel type = 0 (0: Legacy, 1: DSC)
11-14 01:04:46.886 1976 1976 I SurfaceFlinger: Using HWComposer service: 'default'
11-14 01:04:46.888 1956 1956 I HWC2On1Adapter: Found support for HWC virtual displays
11-14 01:04:46.889 1976 1976 I SurfaceFlinger: SurfaceFlinger is starting
11-14 01:04:46.889 1956 1956 E HWC2On1Adapter: Setting active config to 0 for HWC1 config 0
Code:
11-14 01:04:54.226 1976 1976 I RenderEngine: OpenGL ES informations:
11-14 01:04:54.226 1976 1976 I RenderEngine: vendor : ARM
11-14 01:04:54.226 1976 1976 I RenderEngine: renderer : Mali-T720
11-14 01:04:54.226 1976 1976 I RenderEngine: version : OpenGL ES 3.1 v1.r29p0-01rel0.###other-sha0123456789ABCDEF0###
11-14 01:04:54.226 1976 1976 I RenderEngine: extensions: GL_EXT_debug_marker GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth24 GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_EXT_read_format_bgra GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_EGL_sync GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_required_internalformat GL_OES_vertex_array_object GL_OES_mapbuffer GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_type_2_10_10_10_REV GL_OES_fbo_render_mipmap GL_OES_element_index_uint GL_EXT_shadow_samplers GL_OES_texture_compression_astc GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_sliced_3d GL_KHR_debug GL_EXT_occlusion_query_boolean GL_EXT_disjoint_timer_query GL_EXT_blend_minmax GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_OES_texture_3D GL_EXT_texture_storage GL_EXT_multisamp
11-14 01:04:54.226 1976 1976 I RenderEngine: GL_MAX_TEXTURE_SIZE = 8192
11-14 01:04:54.226 1976 1976 I RenderEngine: GL_MAX_VIEWPORT_DIMS = 8192
BUT:
Code:
11-14 01:04:57.239 1976 1976 E HWComposer: loadLayerMetadataSupport: getLayerGenericMetadataKeys failed: UNSUPPORTED (8)
11-14 01:04:57.242 1976 1976 I HWComposer: Switching to legacy multi-display mode
11-14 01:04:57.242 1976 1976 E HWComposer: isConnected failed for display 0: Invalid display
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 7
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 8
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 9
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 10
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 11
11-14 01:04:57.243 1956 2065 E display : [PrimaryDisplay] unknown display attribute 12
11-14 01:04:57.248 1976 2142 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.249 1976 2142 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.249 1976 2143 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.249 1976 2143 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.250 1976 2142 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.250 1976 2142 W SurfaceFlinger: Ignoring VSYNC request while display is disconnected
11-14 01:04:57.250 1976 1976 E HWComposer: getDisplayConnectionType: getDisplayConnectionType failed for display 0: Unsupported (8)
11-14 01:04:57.254 1976 1976 I FramebufferSurface: framebuffer size has been limited to [360x360] from [360x360]
11-14 01:04:58.099 1976 1976 D SurfaceFlinger: Setting power mode 2 on display 0
11-14 01:04:58.099 1956 2065 I hwcomposer: exynos_setPowerMode:: disp(0), mode(2)
11-14 01:04:58.100 1976 1976 D SurfaceFlinger: Finished setting power mode 2 on display 0
This means we still have incompatibility between hwcomposer and android system. I am missing something. I will double check framebuffer and display permissions. And I also noticed that surfaceflinger from Exynos7570 device uses this libraries.
Code:
solis:/system_root/system/bin # readelf -d surfaceflingerj4lte | grep NEEDED
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [android.hardware.configstore-utils.so]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [vendor.samsung_slsi.hardware.configstore-utils.so]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [libbinder.so]
0x00000001 (NEEDED) Shared library: [libcutils.so]
0x00000001 (NEEDED) Shared library: [libdisplayservicehidl.so]
0x00000001 (NEEDED) Shared library: [libhidlbase.so]
0x00000001 (NEEDED) Shared library: [libhidltransport.so]
0x00000001 (NEEDED) Shared library: [libinput.so]
0x00000001 (NEEDED) Shared library: [liblayers_proto.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libprocessgroup.so]
0x00000001 (NEEDED) Shared library: [libsync.so]
0x00000001 (NEEDED) Shared library: [libtimestats_proto.so]
0x00000001 (NEEDED) Shared library: [libutils.so]
0x00000001 (NEEDED) Shared library: [libsurfaceflinger.so]
0x00000001 (NEEDED) Shared library: [libSurfaceFlingerProp.so]
0x00000001 (NEEDED) Shared library: [libc++.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
But newly compiled one uses
Code:
solis:/system_root/system/bin # readelf -d surfaceflinger | grep NEEDED
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [android.hardware.configstore-utils.so]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [[email protected]]
0x00000001 (NEEDED) Shared library: [libbinder.so]
0x00000001 (NEEDED) Shared library: [libcutils.so]
0x00000001 (NEEDED) Shared library: [libdisplayservicehidl.so]
0x00000001 (NEEDED) Shared library: [libhidlbase.so]
0x00000001 (NEEDED) Shared library: [libinput.so]
0x00000001 (NEEDED) Shared library: [liblayers_proto.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libprocessgroup.so]
0x00000001 (NEEDED) Shared library: [libsync.so]
0x00000001 (NEEDED) Shared library: [libutils.so]
0x00000001 (NEEDED) Shared library: [libsurfaceflinger.so]
0x00000001 (NEEDED) Shared library: [libSurfaceFlingerProp.so]
0x00000001 (NEEDED) Shared library: [libc++.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
Either there is a misconfiguration on my device tree or some things have changed with Android 11. I see that system boots to setup screen from adb logs but no display. Let's find what causes this. (kernel, hwcomposer,gralloc, exynos libraries or something else)
GOOOD NEWS AND BAD NEWS:
I successfully built a Lineage 18.1 rom. But due to massive HAL changes, framebuffer and hardware composer incompability, display was never worked. So I decided start from earlier Android version that we hope HWC is working. With the big help of this repository, I prepared an AOSP M build environment with custom surfaceflinger, samsung hardware, and solis device tree (with small changes on smdk7270 device tree). I also worked on kernel. Downgraded binder and mali drivers for Android M. Patched decon framebuffer, lcd and backlight. Built AOSP on Ubuntu 14. Time for good news.
GOOD NEWS: Hello Android on Gear S3
BAD NEWS: Nothing is working except display (touchscreen is also working) and USB. We have a lot of work to do. Now it is time to build and upgrade Android version by version.
I noticed that BEZEL is also working! I think it is working like a middle scroll button of a computer mouse. I did not tested too much. When you rotate bezel, A black mouse pointer comes to screen and page scrolls.
Not sure if you allready find something usefull inside AKI Source...
Gear S3 Root and Kernel Source! (Android Wear Port Thread)
Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3 :) After doing some digging and paying zero attention in class today, I came across the kernel...
forum.xda-developers.com
SEC_Android_Independent_EVT0.0_E7270_BSP_KERNEL.tar.zip
SEC_Android_Independent_EVT0.0_E7270_BSP_u-boot.tar.zip
GitHub - naverlabs/aki: AKI open source repository
AKI open source repository. Contribute to naverlabs/aki development by creating an account on GitHub.
github.com
Only as info...
Best Regards
Hey, good work! I want to thank you @parasetam0l and @adfree for your hard work, just for a smartwatch that has begun to be forgotten.
I have a bit of experience in coding myself and I'll be ready for helping you in whatever testing you need. (After the soldering part is done and all the installation can be done without any -possible- physical damage)
I can't wait to use Wear OS in my watch, I've been reading and waiting for this to happen for sooo long
Is there any significant difference in source code of the SM-R760 and SM-R770?
Only the first one was uploaded by Samsung and I have the second one.
If I'm not mistaken they are the frontier and classic models so they might be identical in firmware.
Hello all,
I am trying to keep this topic as up to date as possible. Due to my job, I haven't been able to have enough time for this project for the last few weeks. But I am doing little things day by day.
adfree said:
Not sure if you allready find something usefull inside AKI Source...
Gear S3 Root and Kernel Source! (Android Wear Port Thread)
Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3 :) After doing some digging and paying zero attention in class today, I came across the kernel...
forum.xda-developers.com
SEC_Android_Independent_EVT0.0_E7270_BSP_KERNEL.tar.zip
SEC_Android_Independent_EVT0.0_E7270_BSP_u-boot.tar.zip
GitHub - naverlabs/aki: AKI open source repository
AKI open source repository. Contribute to naverlabs/aki development by creating an account on GitHub.
github.com
Only as info...
Best Regards
Click to expand...
Click to collapse
@adfree
I looked at this repository. Only kernel and UBOOT source. It is also based AOSP 7. Nothing for Exynos 7270 specific device files. For now, no work needed for kernel side and we have combination SBOOT which allows booting Android. Thank you for your help.
lavasbey said:
Hey, good work! I want to thank you @parasetam0l and @adfree for your hard work, just for a smartwatch that has begun to be forgotten.
I have a bit of experience in coding myself and I'll be ready for helping you in whatever testing you need. (After the soldering part is done and all the installation can be done without any -possible- physical damage)
I can't wait to use Wear OS in my watch, I've been reading and waiting for this to happen for sooo long
Click to expand...
Click to collapse
@lavasbey
At this time no testing needed because of nothing to test I am heavily editing gpu and lcd drivers. When they are done, it will be impossible to physically damage to watch. With USB we can always flash our device even it is dead. For wireless download mode I can not promise anything If some testing needed, I will contact you. Thank you for your good wishes and wanting to help.
I will try to explain what I am doing and I want to reach.
As we know, WearOS is based on AOSP source, but its framework part is closed source. We can say that WearOS is 80% same as full Android. For porting WearOS, we need a donor device system dump. I have
Asus Zenwatch 2 dump: WearOS2 Android 6 (too old),
Mi Watch dump: WearOS2 H MR2 Android 9 (Chinese)
TicWatch Pro dump: WearOS2 H Android 9
Galaxy Watch 4 dump: WearOS3 Android 11.
To run WearOS on a new device:
Copy all system and ramdisk files from donor device to new device.
Replace device specific files (init, fstab, rc files, hardware libraries, vendor libraries, binaries etc which we got from our AOSP build)
Get screen, USB, ADB working and solve errors from logs.
Solve driver issues.
Porting WearOS gets easier after working AOSP on device. We can build necessary libraries from source and replace donor device's libraries with our compiled ones.
My first goal is make AOSP 9 working for porting WearOS2. Because latest WearOS2 based on Android H MR2. My next goal is make AOSP 11 working for WearOS3. We can not use smdk7270 or exynos7580 source directly on Android 9 or 11. Too much compile errors. So I will try to build AOSP version by version and solve problems step by step. We see that AOSP 6 is working. I also built AOSP 7 and it is also working.
After Android 8, things changed. Google divided hardware management to HALs, libraries and services. First stage mount, system as root, vndk system showed themselves. I am solving problems on device tree and samsung libraries for building newer AOSP. Whenever we run AOSP 8, it will be easier to reach AOSP 11 and WearOS3.
I just need some more time. Stay tuned for good news.
Granat1 said:
Is there any significant difference in source code of the SM-R760 and SM-R770?
Only the first one was uploaded by Samsung and I have the second one.
If I'm not mistaken they are the frontier and classic models so they might be identical in firmware.
Click to expand...
Click to collapse
Hello @Granat1,
As I discovered SM-R760 uses tizen_solis_defconfig, SM-R770 uses tizen_pop_defconfig. So their kernel configurations are different. I am working on SM-R760 for now so I am not 100% sure. But I know it's just like you said. They should have same hardware and firmware.
EDIT: I read from another thread, tizen_pop_defconfig may be using for SM-R600 (Samsung Gear Sport) and tizen_solis_defconfig is for SM-R760 and SM-R770 (Gear S3 frontier-classic). As I said I am not sure. I am using tizen_solis_defconfig for Gear S3 SM-R760.
Finally,
Display drivers made me tired. I successfully ported Exynos7570 framebuffer and Mali gpu drivers. I replaced dummy LCD driver with LCD driver from Tizen kernel and solved compilation errors. I also patched decon for right RGB colors. Now display is working as expected. It still needs some operation for always on display but that's enough work for the screen for now.
I compiled AOSP9. As I said, with a working Android 9 porting WearOS 2 will get easier. Here is the proof
I can not pass setup screen, because bluetooth is not working. Tizen's bluetooth initialization procedure is different than Android. Gear S3 uses Broadcom BCM43012. Now I am searching Android devices which use this chip then I will fix the bluetooth.
parasetam0l said:
Finally,
Display drivers made me tired. I successfully ported Exynos7570 framebuffer and Mali gpu drivers. I replaced dummy LCD driver with LCD driver from Tizen kernel and solved compilation errors. I also patched decon for right RGB colors. Now display is working as expected. It still needs some operation for always on display but that's enough work for the screen for now.
I compiled AOSP9. As I said, with a working Android 9 porting WearOS 2 will get easier. Here is the proof
View attachment 5570925
I can not pass setup screen, because bluetooth is not working. Tizen's bluetooth initialization procedure is different than Android. Gear S3 uses Broadcom BCM43012. Now I am searching Android devices which use this chip then I will fix the bluetooth.
Click to expand...
Click to collapse
dude you're doing a great job. Can't wait to flash WearOs on my device if it will be a thing in the future!
Dude, thanks a lot for your work! Amazing
I have a active 2 don't know about coding but I think it could work in R820 too ??
pedromms86 said:
Dude, thanks a lot for your work! Amazing
I have a active 2 don't know about coding but I think it could work in R820 too ??
Click to expand...
Click to collapse
Hello, thank you!
This work is Gear S3 (SM-R760, SM-R770) only. It will not work on other devices.
I took a quick look at the features of GWA2 (SM-R820). It has Exynos 9110 with Mali T720MP1 (which is the same as Gear S3). GWA2 also has USB connection (with soldering), SBOOT from combination firmware (necessary for booting something other than tizen) and kernel source (for android specific code). So yes, it is possible to port WearOS. Porting system part will be easy. Difficult part is porting drivers for example sensors.
Thanks for the great work!!
I am looking forward to this project and wishing you luck!
I am wondering if I can install this port for my device in the future? I have Gear S3 Frontier (SM-R765K) Korean version. Also do I need to solder the usb to the device? Or can I flash it via wireless connection?
Thanks for the good work and good luck!