Dear all,
I'm officially back!
In this post, I'll be keeping track of my ongoing work of fixing the camera on N: I'm using ResurrectionRemix.
Following are logcats for the curious tinkerer to follow:
I purposefully uploaded the files to Filebin.ca as direct downloads, not to Pastebin.com, as these are CatLog saves, and are better viewed with CatLog or MatLog. Better for your eyes, really.
Initial logcat with broken camera, taken w/ CatLog after a cold boot:
Almost the same happened with the libqc-opt.so vendor lib from TheMuppets' S3 Neo tree.
https://filebin.ca/3clHC6XLzoBW/N-after-cold-boot.txt
"All working" Marshmallow logcat: https://filebin.ca/3clJ9YbzZKGJ/2017-09-29-11-39-54.txt
Logcat after fixing libqc-opt.so: https://filebin.ca/3clHlhIIS44I/partial_cold_boot.txt
Camera sensor is apparently accessible, the camera HAL actually loads and the Camera app takes longer to force close , but the loading process halts at a complaint about supported FPS modes being zero or max
Most significant error in log:
Code:
10-05 16:23:59.103 E/QCameraParameters(252): int32_t qcamera::QCameraParameters::initDefaultParameters(): supported fps ranges cnt is 0 or exceeds max!!!
Logcat after replacing/system/lib/hw/camera.msm8226.so with alternate from Moto G: https://filebin.ca/3clLhXW4V9oL/new_cam_error.txt
This one complains about missing symbols. Needs a shim?
Most significant error in log:
Code:
10-05 16:11:50.687 E/HAL (254): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters10KEY_QC_ZSLE" referenced by "/system/lib/hw/camera.msm8226.so"...
UPDATE:
Managed to get the camera interface AND the Camera app UI controls to load, but now we get a " Cannot connect to camera" error.
Logcat: https://filebin.ca/3f21n00JdSs5
Screenshot: http://i66.tinypic.com/11ueuev.jpg
Thanks to: @adityaupreti @sound001 for initial N build
Samsung for being Samsung
The Moto G guys for their work on bringing N to falcon.
Thanks for ur return to Grand 2 bro... Hope we will have STable Nougat soon....
Thanks for hard work?
Thank you for your hard work hope you fix it all
Sent from my Samsung Galaxy Grand 2 using XDA Labs
Its a good news for our grand 2 community.Let's hope that we get a stable nougat rom for this device.
Nice. ☺
and yes i can make bootable nougat roms from galaxy tab 10.1 for our g2 like crdroid,rr n 5.8.2 etc but lets the bugs get fixed on our rr n best of luck sir
WaseemAlkurdi said:
Dear all,
I'm officially back!
In this post, I'll be keeping track of my ongoing work of fixing the camera on N: I'm using ResurrectionRemix.
Following are logcats for the curious tinkerer to follow:
I purposefully uploaded the files to Filebin.ca as direct downloads, not to Pastebin.com, as these are CatLog saves, and are better viewed with CatLog or MatLog. Better for your eyes, really.
Initial logcat with broken camera, taken w/ CatLog after a cold boot:
Almost the same happened with the libqc-opt.so vendor lib from TheMuppets' S3 Neo tree.
https://filebin.ca/3clHC6XLzoBW/N-after-cold-boot.txt
"All working" Marshmallow logcat: https://filebin.ca/3clJ9YbzZKGJ/2017-09-29-11-39-54.txt
Logcat after fixing libqc-opt.so: https://filebin.ca/3clHlhIIS44I/partial_cold_boot.txt
Camera sensor is apparently accessible, the camera HAL actually loads and the Camera app takes longer to force close , but the loading process halts at a complaint about supported FPS modes being zero or max
Most significant error in log:
Code:
10-05 16:23:59.103 E/QCameraParameters(252): int32_t qcamera::QCameraParameters::initDefaultParameters(): supported fps ranges cnt is 0 or exceeds max!!!
Logcat after replacing/system/lib/hw/camera.msm8226.so with alternate from Moto G: https://filebin.ca/3clLhXW4V9oL/new_cam_error.txt
This one complains about missing symbols. Needs a shim?
Most significant error in log:
Code:
10-05 16:11:50.687 E/HAL (254): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters10KEY_QC_ZSLE" referenced by "/system/lib/hw/camera.msm8226.so"...
Thanks to: @adityaupreti @sound001 for initial N build
Samsung for being Samsung
The Moto G guys for their work on bringing N to falcon.
Click to expand...
Click to collapse
If you are porting from Moto G. Use Moto G HAL like on S3 Neo we cannot use our HAL on S5 ROMS.
Στάλθηκε από το GT-I9301I μου χρησιμοποιώντας Tapatalk
Tisenoiazei100 said:
Dear all,
I'm officially back!
In this post, I'll be keeping track of my ongoing work of fixing the camera on N: I'm using ResurrectionRemix.
Following are logcats for the curious tinkerer to follow:
I purposefully uploaded the files to Filebin.ca as direct downloads, not to Pastebin.com, as these are CatLog saves, and are better viewed with CatLog or MatLog. Better for your eyes, really.
Initial logcat with broken camera, taken w/ CatLog after a cold boot:
Almost the same happened with the libqc-opt.so vendor lib from TheMuppets' S3 Neo tree.
https://filebin.ca/3clHC6XLzoBW/N-after-cold-boot.txt
"All working" Marshmallow logcat: https://filebin.ca/3clJ9YbzZKGJ/2017-09-29-11-39-54.txt
Logcat after fixing libqc-opt.so: https://filebin.ca/3clHlhIIS44I/partial_cold_boot.txt
Camera sensor is apparently accessible, the camera HAL actually loads and the Camera app takes longer to force close , but the loading process halts at a complaint about supported FPS modes being zero or max
Most significant error in log:
Logcat after replacing/system/lib/hw/camera.msm8226.so with alternate from Moto G: https://filebin.ca/3clLhXW4V9oL/new_cam_error.txt
This one complains about missing symbols. Needs a shim?
Most significant error in log:
If you are porting from Moto G. Use Moto G HAL like on S3 Neo we cannot use our HAL on S5 ROMS.
Στάλθηκε από το GT-I9301I μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I appreciate your input
But can you clarify further?
I am using files from Moto G LineageOS N, the files being either "virgin" or with some edits. But no, I am not porting a whole ROM from the Moto G.
So what you are alluding to is that I use a whole Moto G camera stack? Yep, I'm already working on that.
waseemalkurdi said:
i appreciate your input
but can you clarify further?
I am using files from moto g lineageos n, the files being either "virgin" or with some edits. But no, i am not porting a whole rom from the moto g.
So what you are alluding to is that i use a whole moto g camera stack? Yep, i'm already working on that.
Click to expand...
Click to collapse
good: Luck
good luck my friend
hope you will continue this and bring the solution to all of us
we're dying to use nougat in stable state
I am a beginner in this thing and don't know how to fix the camera in nougat rom for grand 2. Can you explain me which file to download and where to place it step by step.???
[
Nice man i would really appreciate if you could also take a look at the S3 neo as i've got serious trouble with the camera on nougat!
To be honest - i never done a shim and it seems that the neo needs one but no idea where to start.
Varun Maheshwari said:
I am a beginner in this thing and don't know how to fix the camera in nougat rom for grand 2. Can you explain me which file to download and where to place it step by step.???
Click to expand...
Click to collapse
What he tries to do is far away from a zip you download and install. Patience is the best you can have - itll take more than a while.
I cannot thank you guys enough for your time,for even trying..I'd have donated the active developers but I'm broke af..? thanks a lot..
keep going
Hello Bro is how to solve the camera problem in Noughat rom for samsung galaxy grand -2
download link ??
any patch released ?
Koko2017 said:
any patch released ?
Click to expand...
Click to collapse
Please wait for it Bro.Fixing bugs require a hell lot of time.When he fixes it,he would release it.So don't post anything other than trying to help him fix it.
Related
Here is my port of CM11 to SM-P600, a.k.a lt03wifi. Source was almost entirely derived from the official source for SM-T520 which has almost the exact same hardware.
What works:
screen
wifi
bluetooth
logcat
usb otg storage
sound
microphone
multitouch
auto brightness
external sdcard
gps
softkeys
softkey backlight
flashlight
accelerometer
gyroscope
magnetometer
light intensity sensor
pen (without fancy Samsung menus of course)
both cameras
What doesn't work:
nothing as far as tested
Issues:
performance cpu governor causes sleep of death
stock cm camera app issue (see post below)
Links and how to install
Download link
ODIN flashable recovery
You won't be able to install it via TWRP for SM-P600, it will be complaining about the device name not being lt03wifiue. This is because they are mixing it up with SM-P601, it should be fixed on their side. I haven't tried but it might be the case for other recoveries as well. If you receive this error, flash the above recovery with ODIN and install from there. As a side note, the above recovery has much less features compared to TWRP but it's much faster, so it's better for quick test iterations.
I would be really glad if you can install, test and see what issues you might get.
Sources:
For those interested, here is the device source: https://github.com/ayberkozgur/android_device_samsung_lt03wifi.
You'll need the modified exynos 5420 kernel source: https://github.com/ayberkozgur/android_kernel_samsung_exynos5420
XDA:DevDB Information
CyanogenMod 11 - Note 10.1 (2014) WiFi, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
equilibriumtr
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-05
Thanks so much! I really appreciate the work you devs do. I'll install it this weekend and play with it. Thanks again!
Camera issue
There is a weird camera issue that I can describe as follows:
cm stock Camera app hangs when launched; after this, if killed, it will crash at its next launch and Torch will start crashing as well. This seems normal as the flashlight is probably using the same driver as the camera.
Torch will work if Camera is not launched at all.
If the Google Camera app is downloaded, installed and launched, the stock Camera app will properly launch and work until the next reboot, even if the Google Camera app is closed.
At this point, within the stock Camera app, if the mode is set to Video instead of Picture (the default), the Camera app will launch successfully even after a reboot. After launched, it can go back into the Picture mode no problem. So in other words, launching the Camera app in the Picture mode will freeze the camera and the flashlight until reboot.
This is very weird and I couldn't pin it down. The dmesg dump of the stock Camera app: http://pastebin.com/xPDYRG4X
dmesg dump of the Android Camera app: http://pastebin.com/WaqxQA5E
As you see, they are nearly exactly the same.
It could be a permission issue, a driver issue, a kernel module that's loaded on-demand, I have no idea at this point. I need help. Do any of you guys have any insight as to why this might be the issue?
Update: I tried the first ~10 camera apps in the market and ALL of them work perfectly fine. I think CM camera app is to blame here. Is anyone aware of such a thing on other devices?
I love you, where is your donation button , Sir? I dont use the camera and i can stand the sleep of death(although i know it can be fixed) but you have done something really important, with cm on p600 it is much more possible to be supported as a legacy device on many roms instead of only waiting for samsung and roms based on samsung software. Omnirom, PARom, Aopk are just a compile away with something like p600 working. Congratulations, and i still want to see your donate button.
Thank you!
I replaced the camera app with Google Camera, in recovery, and it seems there are no more problems with it.
Is there any way to make the pen work?
Make sure you are using CAF-NEW for the audio,media, and display HALs. Also, make sure that you have the proper commits in the kernel to coincide with the caf-new hals.
Got the lt03wifiue instead of lt03wifi problem.
I cant flash the recovery that you compiled. It says that md5 does not match on odin 3.07. any suggestions?
installed PhilZ Touch, supposedly based on cwm and still got the lt03wifieu name problem.
Can i change lt03wifieu to lt03wifi flashing a samsung rom from sammobil?
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Yes, I forgot to test the pen and it doesn't work at all. Adding it to the list.
Thank you for your kindness, but I don't think I really deserve a donation here, all I did was adjust the obvious parameters in a ready-made source
equilibriumtr said:
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Click to expand...
Click to collapse
META-INF>com>google>android>updater-script
For its to work i deleted the first line that says:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
Click to expand...
Click to collapse
After that and a data wipe on TWRP the installation went smooth. This will let you to flash the rom and also install cwm recovery that comes with CM roms so you can say bye to TWRP; from then, the "lt03wifieu" is not a problem for me on cwm as @equilibriumtr said. I can now flash the zip with the lines that didnt let me before.
I think we could recover the lost security from deleting that line by adding something like this:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
getprop("ro.product.device") == "lt03wifiue" ||
getprop("ro.build.product") == "lt03wifiue" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
Click to expand...
Click to collapse
Can someone please add the lines instead of deleting them first and try flashing? Since with CWM i dont get the "lt03wifi is not lt03wifiue" error so I dont know if my theory is correct.
Will be testing
Thank you for porting cyanogenmod to our tablet. I will be testing it and report anything that goes wrong.
Does ART work or Dalvik only? 'cause AFAIK you can't select ART in the official Samsung firmware...
Also the Exynos 3 cm port reportedly has got the S Pen working (without samsung's s pen functionalities of course), so you might want to take a look at their sources / repos?
PS: Keep up the good work, having a fully functional cm rom one day would be amazing :fingers-crossed:
r4yN said:
Does ART work or Dalvik only? 'cause AFAIK you can't select ART in the official Samsung firmware...
Also the Exynos 3 cm port reportedly has got the S Pen working (without samsung's s pen functionalities of course), so you might want to take a look at their sources / repos?
PS: Keep up the good work, having a fully functional cm rom one day would be amazing :fingers-crossed:
Click to expand...
Click to collapse
By the way, I always had a working pen in my Note II LTE, even back when only cm 10.2 was available. But I'll look at the pen functionality soon because we will be needing it ourselves.
I looked at the device name issue, rebuilt the source and I got exact same build.prop with the original Samsung ROM:
Code:
ro.product.name=lt03wifixx #This changed
ro.product.device=lt03wifi
ro.build.product=lt03wifi
It's basically TWRP's fault for mixing up SM-P601 (lt03wifiue) and SM-P600 (lt03wifi), it should be fixed on their side. I couldn't try philz touch because goo.im was down. For now, try to use my recovery.
I also tried flashing the recovery I provided with Odin 3.07, it works. Something might be wrong on your side.
jakew02 said:
Make sure you are using CAF-NEW for the audio,media, and display HALs. Also, make sure that you have the proper commits in the kernel to coincide with the caf-new hals.
Click to expand...
Click to collapse
I don't think Qualcomm hardware applies here, lt03wifi is Exynos-based.
Good to see that someone finally directed his attention to CM11 for our P600.
Waiting a long time for a working CM11.
Keep up the good work!!:good:
equilibriumtr said:
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Yes, I forgot to test the pen and it doesn't work at all. Adding it to the list.
Thank you for your kindness, but I don't think I really deserve a donation here, all I did was adjust the obvious parameters in a ready-made source
Click to expand...
Click to collapse
If I'm not mistaken, the difference between Tab models and Note models is that the Tabs don't have an S-Pen. So it's not surprising the S-Pen doesn't work when using a Tab ROM.
Hi ...
equilibriumtr said:
I don't think Qualcomm hardware applies here, lt03wifi is Exynos-based.
Click to expand...
Click to collapse
Dear friend , is this ROM stable for Daily Use ? ( I were porting Ubuntu phone based on TW ROMs but as you made this ... it can have a better base ) ... also , do you know how is the RAM used in this ROM ? ( how much free ? )
With best Wishes
HItman1376
hitman1376 said:
Dear friend , is this ROM stable for Daily Use ? ( I were porting Ubuntu phone based on TW ROMs but as you made this ... it can have a better base ... but , do you know how is the RAM used in this ROM ? ( how much free ? ))
With best Wishes
HItman1376
Click to expand...
Click to collapse
Slow down there, mate - you can't expect a fully stable "Daily-use ready" Rom after just one day
This is still in early testing...and I doubt you can call it "stable" when there is a sleep of death problem
thanks ...
r4yN said:
Slow down there, mate - you can't expect a fully stable "Daily-use ready" Rom after just one day
This is still in early testing...and I doubt you can call it "stable" when there is a sleep of death problem
Click to expand...
Click to collapse
Thanks for the Fast response Dear friend ... Well, if the sleep of dead is all , you can get rid of it by increasing the Min CPU Freq using any CPU manager app ... can you tell me about the RAM ? ( we have RAM management problem in UP so we need some more free RAM comparing with TW ROMs ) ... Thanks in advance
With Best Wishes
Hitman1376
First off thanks for the port. I find stock android roms the best to run Linux on so if you could release a separate kernel with Virtual Terminal enabled (VT_config) it would be great.
As expected the rom only has the barebones on it and seems far more lightweight than even the most debloated rom. Merely not running the Samsung frameworks does wonders me thinks...
Hi guys, I've found a custom rom that seems to work for our XA ultra. I'm using an other phones rom as base.
I don't want to steal someone elses credits and/or work.
I haven't spoken with the author and I'm not aware of all the rules. I fell of the motorcycle when a dog tried to attack me so my hands(palms) are wounded. Feel free to help me on this journey. Finally no more sickening bloated sony rom.
Kernel used: https://forum.xda-developers.com/xa-ultra/development/f32xx-stock-kernel-built-sources-t3639725
System image ROM: AOSP? 7.0 Need to contact author first.
Bugs:
- Battery shows as 1%
- No sound from speaker, MIC works
- Settings System app crashes when opening about phone
- Camera with weird blueish greenish hue/tint
- Share image upload doesn't show file browser
What's working:
- Touchscreen
- Keyboard
- WIFI
- Camera front and rear
- Auto rotate
- SD card
- Vibrations
Pictures:
https://imgur.com/a/vM58t
Contacted author of rom through the pm system
Tahsin88 said:
Pictures:
https://imgur.com/a/vM58t
Contacted author of rom through the pm system
Click to expand...
Click to collapse
Thank you for pictures, you know if the rom have sources?
rrvuhpg said:
Thank you for pictures, you know if the rom have sources?
Click to expand...
Click to collapse
No clue I contacted the author of the rom if it is okay to link his rom in this thread, will ask him if he replies. Not sure if it is an aosp or 7.0 modified to look like one.
I'm just happy we found a non sony rom to work as expected with our phone with minor issues. I did not port the rom just flashed system.img and it seemed to work. No major crashes overheating or anything like that. I know we can replace some files like camera libs so charger to get stuff working properly and maybe fix the settings crash when trying to open about phone with logcat? I know most fixes are listed in porting guide topics so hopefully it will be a piece of cake.
I prefer slim roms over any sony roms. TBH i debloated stock 6.0 rom but the phone was overheating and minor issues so I tried some other roms, i removed the backplate of my phone so I can test and remove thr battery cable to quickly reboot when it's stuck or looping. I have no problem with it since my screen broke I also took twrp backups incase it's needed. The sony threads are just too empty
rrvuhpg said:
Thank you for pictures, you know if the rom have sources?
Click to expand...
Click to collapse
Oh crap I just noticed you provided the kernel I used :good: :highfive:
now the forum is little fired up
I'm excited about the rom im sure devs will hep to make it live working
Finally we have something. I'm still waiting for Android 8 sources to be released
Tahsin88 said:
Hi guys, I've found a custom rom that seems to work for our XA ultra. I'm using an other phones rom as base.
I don't want to steal someone elses credits and/or work.
I haven't spoken with the author and I'm not aware of all the rules. I fell of the motorcycle when a dog tried to attack me so my hands(palms) are wounded. Feel free to help me on this journey. Finally no more sickening bloated sony rom.
Kernel used: https://forum.xda-developers.com/xa-ultra/development/f32xx-stock-kernel-built-sources-t3639725
System image ROM: AOSP? 7.0 Need to contact author first.
Bugs:
- Battery shows as 1%
- No sound from speaker, MIC works
- Settings System app crashes when opening about phone
- Camera with weird blueish greenish hue/tint
- Share image upload doesn't show file browser
What's working:
- Touchscreen
- Keyboard
- WIFI
- Camera front and rear
- Auto rotate
- SD card
- Vibrations
Click to expand...
Click to collapse
Send me the link please?
rrvuhpg said:
Thank you for pictures, you know if the rom have sources?
Click to expand...
Click to collapse
Author is not responding found some related source code that will most likely work for our device aswell!
Forwarded it to user rrvuhpg, lets cross our fingers and hope for the best!!!!
Any more news on this?
appleknight said:
Any more news on this?
Click to expand...
Click to collapse
As said by @Tahsin88 he have forwarded sources code links to me, very big thanks to him :good:. Until now I worked with Elephone P9000 sources code as base and it was good on Marshmallow but for Nougat it uses a lot of files from MM and it's not good. New sources are even better to build Nougat based roms, I have to port them to XA and start building. It will takes some time but it's on the good way
rrvuhpg said:
As said by @Tahsin88 he have forwarded sources code links to me, very big thanks to him :good:. Until now I worked with Elephone P9000 sources code as base and it was good on Marshmallow but for Nougat it uses a lot of files from MM and it's not good. New sources are even better to build Nougat based roms, I have to port them to XA and start building. It will takes some time but it's on the good way
Click to expand...
Click to collapse
What about dt2w? Any progress?
And please don't forget XA Ultra, the bigger one
BlueTR said:
What about dt2w? Any progress?
And please don't forget XA Ultra, the bigger one
Click to expand...
Click to collapse
I worked on dt2w P9000 is not good because needed files are already compiled, I need original .c and .h but they are already compiled in .o so it's like some already chewed food and I can't port the patch from it. I tried with an other patch but it doesn't work because some kernel definitions are different in the code and I'm not good enough to correct this. I think that if I can find the same thing in a 3.18 kernel it will works.
Good news for you, all this work and rom building are made on a F3211 device Now I have this one and a F3112 (XA), I work on it because the XA Ultra community thanked me more than the XA community for my work on Nougat so for me it's normal to work on XAU first and later on XA
rrvuhpg said:
I worked on dt2w P9000 is not good because needed files are already compiled, I need original .c and .h but they are already compiled in .o so it's like some already chewed food and I can't port the patch from it. I tried with an other patch but it doesn't work because some kernel definitions are different in the code and I'm not good enough to correct this. I think that if I can find the same thing in a 3.18 kernel it will works.
Good news for you, all this work and rom building are made on a F3211 device Now I have this one and a F3112 (XA), I work on it because the XA Ultra community thanked me more than the XA community for my work on Nougat so for me it's normal to work on XAU first and later on XA
Click to expand...
Click to collapse
So, I guess it will be harder to succeed. Anyway it's not the end of the world, we may not have dt2w but we will have a working custom rom which is better
Tahsin88 said:
Hi guys, I've found a custom rom that seems to work for our XA ultra. I'm using an other phones rom as base.
I don't want to steal someone elses credits and/or work.
I haven't spoken with the author and I'm not aware of all the rules. I fell of the motorcycle when a dog tried to attack me so my hands(palms) are wounded. Feel free to help me on this journey. Finally no more sickening bloated sony rom.
Kernel used: https://forum.xda-developers.com/xa-ultra/development/f32xx-stock-kernel-built-sources-t3639725
System image ROM: AOSP? 7.0 Need to contact author first.
Bugs:
- Battery shows as 1%
- No sound from speaker, MIC works
- Settings System app crashes when opening about phone
- Camera with weird blueish greenish hue/tint
- Share image upload doesn't show file browser
What's working:
- Touchscreen
- Keyboard
- WIFI
- Camera front and rear
- Auto rotate
- SD card
- Vibrations
Click to expand...
Click to collapse
Can u ported miui9 for xa ultra
Status update? Need for testing?
following
Tahsin88 said:
Hi guys, I've found a custom rom that seems to work for our XA ultra. I'm using an other phones rom as base.
I don't want to steal someone elses credits and/or work.
I haven't spoken with the author and I'm not aware of all the rules. I fell of the motorcycle when a dog tried to attack me so my hands(palms) are wounded. Feel free to help me on this journey. Finally no more sickening bloated sony rom.
Kernel used: https://forum.xda-developers.com/xa-ultra/development/f32xx-stock-kernel-built-sources-t3639725
System image ROM: AOSP? 7.0 Need to contact author first.
Bugs:
- Battery shows as 1%
- No sound from speaker, MIC works
- Settings System app crashes when opening about phone
- Camera with weird blueish greenish hue/tint
- Share image upload doesn't show file browser
What's working:
- Touchscreen
- Keyboard
- WIFI
- Camera front and rear
- Auto rotate
- SD card
- Vibrations
Click to expand...
Click to collapse
Could I possibly get the link for this? I will start developing on it.
I feel like this has died?
I hope not so
Hello Folks,
I'm planning to support the Mi 9 with XASP and i just need the Camera Media Profiles Config File from a AOSP based ROM of Your Device. Could anyone pull it and upload it here for Me!?
Should be in /system/vendor/etc and/or /system/etc...
I'm also searching for a Maintainer for XASP. If someone is interested just PM Me and i'll share the Details with You (You just need to repack/upload from GitHub using a Windows PC or Android Phone once the Month)
Hi, you can find the dump of stock ROM here: https://github.com/TadiT7/xiaomi_cepheus_dump/
Not sure if it changes, but at the moment I'm running GSI AOSP so if you need a dump of the profiles I can upload this one too.
Potato997 said:
Hi, you can find the dump of stock ROM here: https://github.com/TadiT7/xiaomi_cepheus_dump/
Not sure if it changes, but at the moment I'm running GSI AOSP so if you need a dump of the profiles I can upload this one too.
Click to expand...
Click to collapse
Stock is using media_profiles_vendor.xml, not sure if a GSI loads the same File since there are 3 of them. I will try around, thanks for sharing!
Miustone said:
Stock is using media_profiles_vendor.xml, not sure if a GSI loads the same File since there are 3 of them. I will try around, thanks for sharing!
Click to expand...
Click to collapse
I suggest you to take a look here at "video recording" section:
https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
I'm not sure but maybe it can help you out
Potato997 said:
I suggest you to take a look here at "video recording" section:
https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
I'm not sure but maybe it can help you out
Click to expand...
Click to collapse
Looks like i have to use and edit all of them. Thinks i want to do are:
-4K Front Camera Video recording
-Higher default Picture Quality by less compression
-Higher default Mem Cap for Picture Processing
-Higher Bitrates for Audio and Video Profiles
-Higher default FPS Rates on Video Recording
And maybe more if i find something interesting... The Profile from Tadi is btw. a awesome Thing for Me. I always had to download full System for a few Files. That makes everything more easy. Thanks again for sharing!
As reading your requirements this will work with PHHs Treble AOSP 9.0 ROM ?
The project sounds interesting, also it mentions that it comes with Magisk, which Magisk Version is included?
FaserF said:
As reading your requirements this will work with PHHs Treble AOSP 9.0 ROM ?
The project sounds interesting, also it mentions that it comes with Magisk, which Magisk Version is included?
Click to expand...
Click to collapse
PHH Treble AOSP 9 (Vanilla ARM64, NoSU) should be the best Choice
Magisk will come in Stable and Beta (18.1 and 19 right now). Does the Mi 9 has Orange Fox or at least TWRP with working AROMA Support? I have seen Problems with AROMA on the Mi 8 while the Poco F1 can flash the Patch fine (Same Specs and Systems can be used across them). I changed back to AROMA Installers since Magisk Modules are forcing restrictions to the Patch such as Device Security Enhancements and Setup Wizard edits. You can follow Me on GitHub to see what's actually going on.
BR
Can't wait for this! If there is anything I can do to help, let me know.
Miustone said:
Hello Folks,
I'm planning to support the Mi 9 with XASP and i just need the Camera Media Profiles Config File from a AOSP based ROM of Your Device. Could anyone pull it and upload it here for Me!?
Should be in /system/vendor/etc and/or /system/etc...
I'm also searching for a Maintainer for XASP. If someone is interested just PM Me and i'll share the Details with You (You just need to repack/upload from GitHub using a Windows PC or Android Phone once the Month)
Click to expand...
Click to collapse
Hello mate if you still need a maintainer as you mentioned i lovely would do it if you give me detailed instruction how i repack the rom in github cause i never did that.
Uploading somewhere should be no problem but need also the details where i should upload
Cheers
Hi mate,
i´ll tryed now 3x to reply your PM but something goes wrong..... i wrote now a email over xda with the hope it will reach you
Cheers
New Update Available For LineageOS 15.1
Changelog:
*Security update 2021-10-05
Download: https://drive.google.com/file/d/1fdMcQyPemolSdyJSUd8kwznqmorCsRfl/view?usp=sharing
Note : signature spoofing enabled to install microG
Build Date : 30.12.2021
_________________________________________________________________________________________________________
Also for those who encounter sometime a reboot or shutdown (on QuicksilveR kernel) when you have low battery, and lose the hability to
pull down notification bar
use home button
see any notification
Follow this guide (using only ADB and root for ADB) : https://forum.xda-developers.com/k5...0-0-stable-t4028183/post82081237#post82081237
Thanks to @Shreps, @Harry8242, @hsj51 and @Ghostrider_reborn for their help on Telegram and their trees
Security patch : 5th of October 2020
Build date : 16th of October 2020
If some of you are interested, I'll post new builds for security updates.
Source : https://github.com/LineageOS/
Device tree : https://github.com/adinechin/android_device_lenovo_A6020
Kernel tree (QuicksilveR) : https://github.com/ghostrider-reborn/android_kernel_lenovo_msm8916
Kernel tree (DarkKnight) : https://github.com/harry8242/android_kernel_lenovo_msm8916
Vendor tree : https://github.com/adinechin/proprietary_vendor_lenovo
Screenshot
Sent from my Vibe K5 Plus using XDA Labs
I thought I would never see a new Oreo ROM. Will try and provide feedback. Thanks for your work
Sent from my Lenovo Vibe K5 Plus using XDA Labs
I found no bugs or crashes in it. Everything works fine including voLTE. But with stock kernel, the ROM is somewhat laggy and app loading time is longer. It is usable but with stuttering throughout the system. But with Dragon elite kernel, the phone is reasonably smooth and app loading times are noticeably faster. I think that it may be better if you bundle the ROM with PBH kernel or DE kernel instead of stock. People who want to be updated with latest security patches should consider this ROM. Thanks again for this ROM.
Sent from my Lenovo Vibe K5 Plus using XDA Labs
Akash Raj1 said:
I found no bugs or crashes in it. Everything works fine including voLTE. But with stock kernel, the ROM is somewhat laggy and app loading time is longer. It is usable but with stuttering throughout the system. But with Dragon elite kernel, the phone is reasonably smooth and app loading times are noticeably faster. I think that it may be better if you bundle the ROM with PBH kernel or DE kernel instead of stock. People who want to be updated with latest security patches should consider this ROM. Thanks again for this ROM.
Click to expand...
Click to collapse
Thanks for your feedback. I've tried to build the ROM directly with a non stock kernel, but I did not succeed, and I let the users choose one
Sent from my Vibe K5 Plus using XDA Labs
adinechin said:
Thanks for your feedback. I've tried to build the ROM directly with a non stock kernel, but I did not succeed, and I let the users choose one
Click to expand...
Click to collapse
Okay, fair enough. Looks like voice calling quality also improved. In previous Oreo ROMs, people in the other end had echoeing issues when I used my earphones but in this ROM, it's gone and they said that my voice sounds much clear and loud. So it's gonna be my daily driver:victory:
Sent from my Lenovo Vibe K5 Plus using XDA Labs
Pbh and dragonelite reduces internet speed
Use harry8242 darkknight 3.10.108 kernel instead
good work, man, i'm on Blaziken kernel, smooth, fast enough, thnx ⁴ ur work, man!
only one question: what i've 2 do to make "quick unlock when right pin entered"??? any suggestions, except exposed, don't like it, are suitable(/system files change etc.)
bhadanamayank said:
Pbh and dragonelite reduces internet speed
Use harry8242 darkknight 3.10.108 kernel instead
Click to expand...
Click to collapse
As @Harry8242 advised me, I'll try to make a new build :
with the kernel from Pie that should work
without the HYPER reference in the name because I'm not part of this team
Hello, I wish you success in the new ROMs with the priority of Edirne.Linegeos Rom I've tried, pretty simple but very stable and useful, of course I wonder, when I'm dealing with the new structure different from a la Linegeos ROMs are you trying?(viperos,Resurrection remix,like dotos) I'll be very happy if at least one update in it if your good work in my own way
good work :good::good::good:
Is the camera working? (from whatsapp, gcam and etc).
DnlPereira said:
Is the camera working? (from whatsapp, gcam and etc).
Click to expand...
Click to collapse
Everything works good
Bug
I'm sorry I don't know how to navigate here, well the only bug I found was that when he makes a sound he makes a little "beep" noise. Can you fix this? It is very annoying.
When receive notification too (Sorry my bad english)
Hi everyone, for those interested, I've successfuly built a new version with @Harry8242 Pie kernel which is working and thus fixing the Instagram/WhatsApp videos bug, this build contains september security patch.
I'm currently doint a new build including my personal customization : having by default 3 lines of notification tiles
As soon as it's ready, I will share it
Hi everyone, for those interested, I've successfuly built a new version with @Harry8242 Pie kernel which is working and thus fixing the Instagram/WhatsApp videos bug, this build contains september security patch.
I'm currently doint a new build including my personal customization : having by default 3 lines of notification tiles
As soon as it's ready, I will share it
As promised new update : https://drive.google.com/open?id=1itsb0KURhZ0XrM3vuT-buRiYQfTytPe0
September security patch
WhatsApp and Instagram videos bug fixed (using @Harry8242 Pie kernel)
No more "HYPER" on the ROM name
Only personal customization : 3 lines of notification tiles
adinechin said:
As promised new update : https://drive.google.com/open?id=1itsb0KURhZ0XrM3vuT-buRiYQfTytPe0
September security patch
WhatsApp and Instagram videos bug fixed (using @Harry8242 Pie kernel)
No more "HYPER" on the ROM name
Only personal customization : 3 lines of notification tiles
Click to expand...
Click to collapse
Thanks for removing the tag
The rom is smooth. Real smooth Even recording on stock camera app works.
I'd like to ask you to remove that "turn off mobile data" dialog when turning off cellular data toggle, please.
eurodiesel said:
The rom is smooth. Real smooth Even recording on stock camera app works.
I'd like to ask you to remove that "turn off mobile data" dialog when turning off cellular data toggle, please.
Click to expand...
Click to collapse
I don't know where I can do that but I'll try
Sent from my Vibe K5 Plus using XDA Labs
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
IMPORTANT INFORMATION
Hi all,
This is an unofficial Pie build for the Galaxy Note 2 (t0lte) based on LineageOS 16.0.
Most of the ROM features are working, but the overall state might be not fully stable or not suitable for a daily use.
This work is heavily based on works of PoisonNinja, Option58 (thanks for device tree, kernel and device patches for LOS 14.1).
A full credit for Pie bringup goes to rINanDO (thanks for device tree, kernel and device patches for LOS 16.0).
What is working:
Boots
Audio (playback && recording)
Bluetooth
Graphics
Camera
Sensors
RIL (SMS, mobile data, calls)
Wifi
USB
Video playback (HW/SW)
What is not working:
GPS
Compass / Magnetic Sensor
SIM might be not detected / Data might be not available upon boot (reboot to fix).
LTE is not currently supported
Gapps installation can cause boot issues (?) - not tested
Supported variants:
fully tested on t0lteatt (SGH-I317, AT&T variant)
SGH-I317M
SGH-T889
Should also work for the following variants (not tested as of now):
GT-N7105/N7105T
SGH-T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Reporting bugs
When reporting reboots, please produce log below as follows
(using adb or terminal)
Code:
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
and attach in this thread.
If reporting another issues
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
A rough timestamp of when the issue occurred is also useful.
Click to expand...
Click to collapse
Download:
ROM
TWRP
Root
Installation:
Make sure you are using the latest TWRP version.
Download the latest build and copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Flash LineageOS 16.0
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Set up everything and reboot again to get radio working
Credits:
rINanDO
forkbomb444
Option58
PoisonNinja
AdrianDC
A$teroid
Lord Boeffla
LineageOS team
Nameless ROM
I really do hope I didn't miss here anyone who deserves credits for their amazing works
If you like my work and want to thank me, feel free to buy a coffee
Source code: LOS 16.0
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy Note II
Contributors
ChronoMonochrome, rINanDO, Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/CustomROMs/android_local_manifests_i9300/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.2.x or newer
Version Information
Status: Testing
Created 2020-01-02
Last Updated 2020-01-02
Reserved
Reserved
Congrats on getting this working! :victory:
This build work for me cool thé ril work il so happy to see pie on this device thank
Hi,
thanks for your hardwork on this. Unfortunately doesnt work on SHV E250:
This package is for device: tolte, t0ltexx, gt-7105, t0lteatt, SGH-I317M...... this device is .
updater process ended with Error:7
Working on N7105 blazing fast. haven't tried with gapps.
sosodef_3000 said:
Hi,
thanks for your hardwork on this. Unfortunately doesnt work on SHV E250:
This package is for device: tolte, t0ltexx, gt-7105, t0lteatt, SGH-I317M...... this device is .
updater process ended with Error:7
Click to expand...
Click to collapse
I had a similar error with my t0lte. I was able to fix my error by installing the latest TWRP
qspitzer said:
I had a similar error with my t0lte. I was able to fix my error by installing the latest TWRP
Click to expand...
Click to collapse
what version of note 2 do you have?
sosodef_3000 said:
what version of note 2 do you have?
Click to expand...
Click to collapse
I have the AT&T (i317/t0lteatt) version
i test this rom on my Samsung Note 2 SHV-e250k and it was good but sometimes buggy
You can activate the LTE option on *#*#4636#*#* but sometimes the "No Internet" appears
Pico is the best to install gapps because when you use other it was not working because of "System is full" message
sometimes the facebook, messenger and youtube crash and i encounter the Couldn't sign in on Google
again it's a good rom and need some several fix tho, it was good already just fix the Google Account issue, the partition of Sys on the memory and some app crashes.
Thanks for your work on this ROM ChronoMonochrome!
I tested out your ROM on my Verizon Galaxy Note II (t0ltevzw), another Note II LTE variant. I had to modify the updater-script to get this ROM to flash successfully on my device. Everything seems to be working (sound, wifi, BT), except for RIL. I seem to be seeing a dialog on launch saying that the SIM is voice only.
I'm guessing this is due to some specific differences with t0ltevzw compared to other t0lte devices.
Let me know if there's anything I can do to help with testing.
Sent from my GM1917 using Tapatalk
CKTurbo128 said:
Thanks for your work on this ROM ChronoMonochrome!
I tested out your ROM on my Verizon Galaxy Note II (t0ltevzw), another Note II LTE variant. I had to modify the updater-script to get this ROM to flash successfully on my device. Everything seems to be working (sound, wifi, BT), except for RIL. I seem to be seeing a dialog on launch saying that the SIM is voice only.
I'm guessing this is due to some specific differences with t0ltevzw compared to other t0lte devices.
Let me know if there's anything I can do to help with testing.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Hi,
this variant of N7105 seems to be unsupported even by the official LineageOS sources.
You can try extract file libsec-ril.so from the stock and try use it (put the file in /system/lib).
If that works, it should be easy to add support for this phone variant as well.
ChronoMonochrome said:
Hi,
this variant of N7105 seems to be unsupported even by the official LineageOS sources.
You can try extract file libsec-ril.so from the stock and try use it (put the file in /system/lib).
If that works, it should be easy to add support for this phone variant as well.
Click to expand...
Click to collapse
Thanks @ChronoMonochrome. I've added the libsec-ril.so from the latest t0ltevzw KK stock ROM.
After doing so, the SIM card dialog warnings have gone away and the phone number is now detected on the Verizon SIM card.
Still no radio signal (at least for Verizon), but probably related to another issue.
t0ltevzw 4.4.2 KitKat Stock libsec-ril.so:
https://gitlab.e.foundation/e/devic...0ltecdma/proprietary/system/lib/libsec-ril.so
Sent from my GM1917 using Tapatalk
View attachment 4923377
CKTurbo128 said:
Thanks @ChronoMonochrome. I've added the libsec-ril.so from the latest t0ltevzw KK stock ROM.
After doing so, the SIM card dialog warnings have gone away and the phone number is now detected on the Verizon SIM card.
Still no radio signal (at least for Verizon), but probably related to another issue.
t0ltevzw 4.4.2 KitKat Stock libsec-ril.so:
https://gitlab.e.foundation/e/devic...0ltecdma/proprietary/system/lib/libsec-ril.so
Sent from my GM1917 using Tapatalk
View attachment 4923377
Click to expand...
Click to collapse
I didn't know it's a CDMA device. CDMA is not supported by the ROM, however the following can make it work.
Edit /system/build.prop as following:
Code:
rild.libpath=/system/lib/libsec-ril.so
(change rild.libpath=/system/lib/libsecril-shim.so to rild.libpath=/system/lib/libsec-ril.so)
This is very promising ROM even though the basic issue I can say it is constant need to restarting to use data and even the music app starting at any time to is also a problem. Apart from that, this is a dream come true
ChronoMonochrome said:
I didn't know it's a CDMA device. CDMA is not supported by the ROM, however the following can make it work.
Edit /system/build.prop as following:
Code:
rild.libpath=/system/lib/libsec-ril.so
(change rild.libpath=/system/lib/libsecril-shim.so to rild.libpath=/system/lib/libsec-ril.so)
Click to expand...
Click to collapse
Thanks for the suggestion! Yep, the Verizon Galaxy Note II is CDMA. I tried making the build.prop settings and then added the Verizon APN, but still no signal found.
Not a big deal, since I'm just using it on Wi-Fi at the moment.
As for Gapps issues, I have the Gapps pico package installed. However, I noticed that if you install a certain Google app (not sure, could be Google, Google Assistant, Gmail, etc), it causes bootloops to occur. I've had to factory reset a few times. Trying to figure which Google app causes this to occur.
Sent from my GM1917 using Tapatalk
shv e250k
KirikoSen said:
i test this rom on my Samsung Note 2 SHV-e250k and it was good but sometimes buggy
You can activate the LTE option on *#*#4636#*#* but sometimes the "No Internet" appears
Pico is the best to install gapps because when you use other it was not working because of "System is full" message
sometimes the facebook, messenger and youtube crash and i encounter the Couldn't sign in on Google
again it's a good rom and need some several fix tho, it was good already just fix the Google Account issue, the partition of Sys on the memory and some app crashes.
Click to expand...
Click to collapse
Hi thanks for this.
Did you change the updater script to get it to work? Because mine it justs stops trying to install and says this is for phones....etc
Also what bands (wcmda/LTe) did you select for the *#*#4636#*#* ? I tried this on my oreo 8.1 but this didnt find the IMEI or the sim
(Also it seems you tested this in the past...what new rom did you move on to?)
I've been investigating further into why this ROM starts bootlooping or experiences the display to blackout, particularly with t0ltevzw. One suspicious error seems to be with com.google.android.carriersetup:
2020-01-12 09:38:46.929 18771-18771/system_process E/PackageManager: updateAllSharedLibrariesLPw failed: Package com.google.android.carriersetup requires unavailable shared library com.verizon.provider; failing!
2020-01-12 09:38:49.606 18771-18879/system_process E/StorageManagerService: Failed to read field SystemLocale
android.os.ServiceSpecificException: Failed to read field SystemLocale (code 2)
at android.os.Parcel.createException(Parcel.java:1964)
at android.os.Parcel.readException(Parcel.java:1918)
at android.os.Parcel.readException(Parcel.java:1868)
at android.os.IVold$Stub$Proxy.fdeGetField(IVold.java:1112)
at com.android.server.StorageManagerService.getField(StorageManagerService.java:2427)
at com.android.server.StorageManagerService.copyLocaleFromMountService(StorageManagerService.java:984)
at com.android.server.StorageManagerService.handleDaemonConnected(StorageManagerService.java:977)
at com.android.server.StorageManagerService.access$900(StorageManagerService.java:173)
at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:574)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.os.HandlerThread.run(HandlerThread.java:65)
Click to expand...
Click to collapse
logcat: View attachment 4925079
These symptoms seems to start occurring if you install any of these `com.google.*` apps:
* Google Wellbeing
* Google Calendar
* Gmail
* Google Docs
* Google Slides
Finally got this to load on SHV-E250K but unfortunately internet doesnt work.
If Chronomonochrome can kindly fix that would be great.
Tried to reflash the old modem from 4.4.2 but that didnt help.
tried murata fix and flashed together still didnt work
Have gone back to:
lineage-14.1-20171208-nightly-t0ltekor-signed with wifi and internet working.
Maybe someone can take the wifi files from there and plug into lineage 16.0 that would be great