Related
Obsolete
This workaround was only relevant some time ago while custom kernels did not yet have updated sources from Samsung to work on 4.0.4 ROMs. This is no longer the case so this info is completely irrelevant now.
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix for it.
Installation
Just take the CWM zip file and apply it on your ROM. It will leave a backup of the 2 files that will be replaced.
Removal
The Restore zip can be "installed" to remove the patched files and put back the original ones that were kept on your device.
Tested and working both for Camera preview and Video playback, on XWLPM.
Note: This is a temporary fix until the kernel devs have enough information to properly update their code, and when that happens this fix can be uninstalled.
Heyy Tungstwenty, another great fix by you!
Well done, it works great! Now also videoplayback works fine with siya on 4.0.4!
Now the only thing left not working on 4.0.4 with Siya is the bluetooth...
Thanks again!
he he he go 4.04 gooo!
Thanks man.
Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Thanks for the tips!
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
Click to expand...
Click to collapse
I actually had that happen to me when i was on Neat Rom. Don't know what caused it but I ended up switching roms.
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Click to expand...
Click to collapse
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Tungstwenty said:
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Click to expand...
Click to collapse
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
The Undertakerr said:
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
Click to expand...
Click to collapse
I don't think it's offtopic
This is indeed very strange, but here's a possible explanation:
The custom kernels (Siyah, Dorimanxx, ...) each have their own tweaks; they're not exactly the same. While they might share lots of common changes and improvements, they do have different things hence the word "custom".
There's a possibility that the sequence of events to make the camera work is contained not only on the binaries (the ones in the zip file I posted), but also on some cached data that was already picked up when you first ran the camera app, which invoked a service, which in turn invoked a library, etc. Later, when reopening the camera, now with the "fixed" binaries, there might still be bad data that a particular kernel is not expecting. Even if you came from Siyah when initially running the camera app, the original libraries might have cached strange data that the kernel will no longer recognize even after the binaries are now in line with the kernel. And another kernel might have code that is lenient enough to still work with it.
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah
Tungstwenty said:
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix
Click to expand...
Click to collapse
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Click to expand...
Click to collapse
I have worked on this fix using XWLPM as a secondary ROM (I'm still on XWLPG) but this should work both for LPM and LQ5.
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Sent from my GT-I9100 using xda app-developers app
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
cdaarif said:
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Click to expand...
Click to collapse
This is just a fix for Camera + Video. I know bluetooth is also not working but as I posted before, I tried to fix it as well but don't think it's doable without changing the kernels. Kernel devs will have to find a way to fix it.
Working bluetooth on LPM with stock Kernel and camera with your hack.
marbutina said:
Working bluetooth on LPM with stock Kernel and camera with your hack.
Click to expand...
Click to collapse
If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.
Thanks.
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
hardcore said:
Well whaddaya know...
K3-9:
- Bluetooth now works for 4.0.4 ROMS
Click to expand...
Click to collapse
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Krendelrus said:
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Click to expand...
Click to collapse
Thanks for the above info!
Best to repeat this message in the Siya thread, and/or send Gokhanmoral this info by PM. He might be able to use Hardcore's sources to fix bluetooth in Siya kernel...
Edit: I see you allready did that. Thanks again! Maybe soon we can have working bluetooth with a custom kernel, that would be great!
Hello,
This is my first post, I hope to be more active on the forums in future as I think its a great community.
I've flashed the new and wonderful AOSP rom by Maclaw but am unable to get S2E to work. It just stays greyed out.
Things I did (after standard procedures such as mount as EXT4):
- Installed init.d (not sure if required, but tested, working) also tried to install it before installing S2E along with the patches.
- Applied some of the patches available for CM9 (S2E_Android.zip and sd-ext_patch-signed-v11.zip)
- Tried if link2sd recognized the partition and how it works with EXT. It did work (I think, no notification after reboot) but I dont see this as a viable alternative (but maybe someone can convince me it in fact, is)
- Tried without 'mount as EXT4'
I'm looking for alternatives for S2E that could work on this mod, or a solution to get this to work. Any solutions would be greatly appreciated!
S2E works only on cm7, cm9 and cm10.
There is no init.d support on this rom but you can add it when you look at this thread:
http://forum.xda-developers.com/showthread.php?t=1933849
I use link2sd and it works great. Open Link2sd and then select ext4 (or which sd ext you have) reboot your phone and open link2sd again and open settings and click on auto link ... also select auto link dex + auto link apk + auto link lib. So you don't have to do it yourself when you install an app.
It's aosp ics so i don't think cm9 patches will work.
Sent from my GT-S5660 with AOSP ICS from MaclawStudio.
Yeah. I didn't realise link2sd does have a similar feature (use ext for dalvik data etc). I chose this name for a reason lol.
Btw, we have the same rom and I love it compared to their alpha. Is the calendar not working for u either? I'm unable to make new events.
Sorry for asking here, but cannot post in dev yet to report it (its not in their 'not working' list so maybe u can report or have a solution)
Thanks
Sent from my GT-S5660 using xda app-developers app
Junior, could you find some app to move the dalvik to SD on Maclaw's ROM already?
FlemishDroid said:
S2E works only on cm7, cm9 and cm10.
...
I use link2sd and it works great.
...
Click to expand...
Click to collapse
There is no doubt that Link2SD is a very good app.
The problem is that it doesn't move /data/data folder which in Maclaw's ROM is huge compared with other CM7 ROMs.
So, the question remains. What can be done to fix S2E or what other solutions exists?
Cyanogenmod 11.0
Download:
http://dualhoki.vim.hu/bubor/dev/11.0/
http://rpi.bubor.hu/bubor/dev/11.0/
Changelog:
20131229: enable dynamic fsync, selinux is enforcing (break wifi)
20131230: add camerawrapper back, fix wifi
20131231: 2 phone app again, selinux enforcing
20140104: happy new year! Torch uses camera interface again (it fixes strobe crash), update CM 11, and patches to latest CM 11, selinux is permissive ( you can check settings -> about phone )
20140109: fix OTG storage mount (thanks karthik050782), remove google dialer (thanks tonyp)
20140118: only cm update
20140131: bln light fix.
20140222: cifs and nfs support
20140402: ksm (settings -> performance -> memory -> KSM) saves memory, cm update
20140601: remove gmaps
20140607: android 4.4.3
20140627: android 4.4.4
20140702: include skype fix ( you still need to run alsas
20140911: updated kernel for better battery life, thanks mara-
20150814: update cm (latest commit included )
20151224: update cyanogenmod, and gpu reserved memory lower to 192MB, xposed fix thanks BgiSock
20151230: revert gpu reserved to 256mb and skia fix ( open a gif crashed)
20160126: some tweak
20161001: end of life, no cyanogemod update released, I stop to build.
Install:
* Read this
* To safe start with stock, boot at least once to stock ( you can ignore this step, but you might have issues)
* Use my latest TWRP.
* Factory reset( you may skip this, but dont report bugs)
* Install zip
* Enjoy
Issues:
If you have issue, please repeat installing steps, but start with flash stock with odin, and boot once with stock.
No sound with skype, no bt call sound. Fix
Capture picture and video has fixed rotation.
Video recording may crash with default (only?) app
Gps works, readthis fix
Some app doesnt support our device, try older version, read this for list
Google play service crashes use this , or never from store
Tell me
addons:
Face unlock support: http://dualhoki.vim.hu/bubor/dev/faceunlock.zip
Swap internal external sd: http://dualhoki.vim.hu/bubor/dev/change-fstab.zip ( it replaces fstab.n1, it should work with all KK)
Old topic was: http://forum.xda-developers.com/showthread.php?t=2588304
XDA:DevDB Information
Cyanogenmod 11, ROM for the Samsung Captivate Glide
Contributors
bubor
Source Code: https://github.com/buborh/android_device_samsung_i927/tree/cm-11.0
XDA:DevDB Information
Cyanogenmod 11, ROM for the Samsung Captivate Glide
Contributors
bubor
Source Code: https://github.com/buborh/android_device_samsung_i927/tree/cm-11.0
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Created 2014-07-02
Last Updated 2017-03-27
Reserved
Reserved
When you say Skype fix is included, what do we, the users, need to do to get it working automatically? Just run alsas command or we need to follow the guide with tasker? Also, YouTube is crashing, I suppose because of Tegra? Do you or anyone else knows which is the last working version?
mara- said:
When you say Skype fix is included, what do we, the users, need to do to get it working automatically? Just run alsas command or we need to follow the guide with tasker? Also, YouTube is crashing, I suppose because of Tegra? Do you or anyone else knows which is the last working version?
Click to expand...
Click to collapse
skype fix is what you download from zip, you need to run alsas, config tasker etc, but you dont install that zip from recovery.
Thanks for the info and for your effort, of course. To anyone interested, latest YouTube working for me is 5.7.41.
Hi, after connecting i927 to PC using USB cable, I cant see the green android icon to confirm that I want to use the phone as a disk drive. Is it normal or something wrong happened to my glide?
irekd said:
Hi, after connecting i927 to PC using USB cable, I cant see the green android icon to confirm that I want to use the phone as a disk drive. Is it normal or something wrong happened to my glide?
Click to expand...
Click to collapse
try to go settings -> storage click menu button or right top corner, usb computer connection.
Be sure usb debug is disabled ( default is disabled).
Because netflix closes when trying to open it? Any solution to this problem?
Sent from my SGH-I927 using XDA Premium 4 mobile app
Bubor, thank you once again for all your updates!
Everything is smooth as usual, but starting from 4.4.3 the battery in idle is draining way faster than before. The thing is simple: the phone never goes into deep sleep. Active time is 100% when charger is unplugged. Updating to 4.4.4 didn't fix the problem.
Further narrowed this issue: it comes with Google Play Services updated to 5.0.X. It just active all the time, even if not using CPU power at all. Restored it from backup to 4.4.52, now the phone sleeps again.
Makshow said:
Bubor, thank you once again for all your updates!
Everything is smooth as usual, but starting from 4.4.3 the battery in idle is draining way faster than before. The thing is simple: the phone never goes into deep sleep. Active time is 100% when charger is unplugged. Updating to 4.4.4 didn't fix the problem.
Further narrowed this issue: it comes with Google Play Services updated to 5.0.X. It just active all the time, even if not using CPU power at all. Restored it from backup to 4.4.52, now the phone sleeps again.
Click to expand...
Click to collapse
would you try gapps from here: http://forum.xda-developers.com/showthread.php?t=2397942 ?
Where did you found google play 5.0.x? https://play.google.com/store/apps/details?id=com.google.android.gms only 4.4.52
bubor said:
would you try gapps from here: http://forum.xda-developers.com/showthread.php?t=2397942 ?
Where did you found google play 5.0.x? https://play.google.com/store/apps/details?id=com.google.android.gms only 4.4.52
Click to expand...
Click to collapse
Yes, I tried to update Google play services from pa gapps before posting. (installed Play Services Update Module). Last update was july, 2 (as in the store), but the version number was showing 5.0.84.
Makshow said:
Yes, I tried to update Google play services from pa gapps before posting. (installed Play Services Update Module). Last update was july, 2 (as in the store), but the version number was showing 5.0.84.
Click to expand...
Click to collapse
but my rom includes an old one, it should work without installing gapps.
bubor said:
but my rom includes an old one, it should work without installing gapps.
Click to expand...
Click to collapse
I've got 4.8.20 and it still eats the battery quite fast. And I must say that I'm always trying to do things that should make the battery last longer:
1. I usualy use 2G (switch to 3G only when using internet)
2. I turn off wifi when not needed
3. I switch the phone in airplane mode for the night.
4. I use Greenify app for freezing apps which are set to work in background and I don't need them to work that way.
5. Turn on bluetooth and GPS only when needed.
Like @Makshow I also noticed that the phone isn't going into deep sleep almost at all.
irekd said:
Click to expand...
Click to collapse
what app this is?
bubor said:
what app this is?
Click to expand...
Click to collapse
AeroControl by @Blechd0se from Motorola Defy XDA thread. Very nice app.
Hello bubor please check netflix not fount thanks
Sent from my SGH-I927 using XDA Premium 4 mobile app
victorsalas said:
Hello bubor please check netflix not fount thanks
Sent from my SGH-I927 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you should be more detailed.
bubor said:
but my rom includes an old one, it should work without installing gapps.
Click to expand...
Click to collapse
That google play services updated themselves to 5.0.82 before my manual update. And one shouldn't upgrade them manually from pa gapps, that update broke push messages for me.
Old gapps in this ROM has Services version 4.4.51-038, the -038 part means this version is for 480 DPI screen, while we have 240 DPI. Maybe, that was the reason why they updated themselves when I installed 4.4.3 ROM. Or maybe, they are just updating on some schedule...
I downloaded this file: Google Play Services 4.4.52 (1174655-034) from xda, and it's good so far - push is working, phone is sleeping. Will test some more.
Camera issue
Hi,
After a few days using 20140702 rom, I started to have problem with camera. It crashes all the time it's being run. Yeah, I know that @bubor wrote in OP that one of the issues is: "Video recording may crash with default (only?) app", but it's video recording, and I have crashes with camera. What's more strange is that the camera worked OK through a few days since installing the rom.
I've already cleared cache and data in the camera properties. I've even cleared cache and dalvik cache from TWRP level. And nothing. The camera still crashes. Any suggestions?
One more thing. During the last night my device rebooted. I wouldn't even know this, but I looked to uptime statistics of lately mentioned AeroControl app. Do you guys have such unexpected reboots?
---
Edit: the problem with camera has been resolved. It was just about full internal storage. After making some room, the camera started to work again.
Hi folks,
I'm not sure if found a bug or a feature ... however ... since the integration of SuperSU into any custom rom (CM 12 / Liquid Smooth / PA) based on Lollipop, I'm not able to install more then 8 apps alongside Google Play (sd-card / LAN / USB). Exactly after the 8th app installation the "install now" button isn't pressable anymore. The button is not grayed out or something, it simply doesn't react on pressing. Also when i use apps that needs root access, the question from SuperSU appears, but the "grant" button does not react after the 8th attempt. My internal card has 22 GB free, so that's not the cause i think. I've checked all the system security options for a suspect option, but i haven't found anything yet. Installations via Google Play works fine anyway. Under KK based roms there is no such a strange thing, and as i mentioned above, this was after the integration of SuperSU in LL based roms. Does anyone have an idea what it could be ? ...
sincerely,
LP
luckypeanut said:
Hi folks,
I'm not sure if found a bug or a feature ... however ... since the integration of SuperSU into any custom rom (CM 12 / Liquid Smooth / PA) based on Lollipop, I'm not able to install more then 8 apps alongside Google Play (sd-card / LAN / USB). Exactly after the 8th app installation the "install now" button isn't pressable anymore. The button is not grayed out or something, it simply doesn't react on pressing. Also when i use apps that needs root access, the question from SuperSU appears, but the "grant" button does not react after the 8th attempt. My internal card has 22 GB free, so that's not the cause i think. I've checked all the system security options for a suspect option, but i haven't found anything yet. Installations via Google Play works fine anyway. Under KK based roms there is no such a strange thing, and as i mentioned above, this was after the integration of SuperSU in LL based roms. Does anyone have an idea what it could be ? ...
sincerely,
LP
Click to expand...
Click to collapse
do you have an screen overlay app(like lux) installed and try flashing chainfires 2.38 beta it contains bugfixed for lollipop
suljo94 said:
do you have an screen overlay app(like lux) installed and try flashing chainfires 2.38 beta it contains bugfixed for lollipop
Click to expand...
Click to collapse
Tanks a lot for your response. Yes in deed I'm using Lux. Ok I will test it and will report back.
luckypeanut said:
Tanks a lot for your response. Yes in deed I'm using Lux. Ok I will test it and will report back.
Click to expand...
Click to collapse
try disabling lux
[Solved]
suljo94 said:
try disabling lux
Click to expand...
Click to collapse
OK it's solved. Only deinstalling of Lux doesn't helped. I've installed the latest CM12 (from Today) and in addition the latest SuperSU (2.38). That's worked.
Thx a lot for yours help ! :victory:
sincerely,
LP
I'm not responsible for any damage to your device.
By flashing this you take responsibility of anything that happens to it.
Process at your own risk!
AND FEEL GOOD!
Now it is time to upgrade our P901 to Android 10 QWork
Almost all, I thinks but please give a feedback for any problem and suggestion.
Now P901 can make gsm call / sms / full cellular network.
BT SCO voice call working perfectly on narrow/wide band.
Preinstall v4afx to data partition and working good.
Camera (internal app) can take picture only now.
Video recorder working with app ,like HedgeCam 2, which supports Camera2 API.
Known Issues
- Video recording not working
- S-pen randomly freeze and reboot, still.
- Feedback sound enable will breaks Sound system, Don't enable any feed back sound.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Sources:
https://github.com/Lineageos
https://github.com/LineageOS/android_hardware_samsung
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos5
https://github.com/khomsn/android_hardware_samsung_slsi_openmax
https://github.com/khomsn/android_hardware_samsung_slsi_exynos5420
Kernel: https://github.com/khomsn/android_kernel_samsung_v1a3g
Device: https://github.com/khomsn/device_samsung_v1a3g
Vendor: https://github.com/khomsn/vendor_samsung_v1a3g
THANKS & CREDITCredit to All developers that do share codes to our community and Thank to all of them and you , that makes this ROM.
Spacial Thanks to Valera1978 and ShevT for his kernel base / device prototype.
Spacial Thanks to universal5433 for device prototype.
Credit to v4afx developer viper4android
ROM DOWNLOAD / Change Logs go to Post # 2.
Download ROM Here16/11/21 Last update (11/11/21 broke the bluetooth sco) now fixed.
Spen still random freeze and reboot.
Don't enable Touch sound , it will break sound system.
11/11/21 Working Camera, and Auto Call Recorder (if it is allowed in your area)
now preinstall ViperFx , Galaxy Store , to Data partition if it not yet install,
Spen is fixed ( I hope , Thanks to ShevT for fixed, I applied his patch so, he said no more freeze and reboot).
31/8/21 ViperFx work
Remove Viper4Android for preinstall but still include lib, you must install Viper4Android , I use this package and it work, viperfx_2.7.2.1.apk . This version you can Change , cpu governor, swappiness, mount-bind ext sd card folder to internal folder.
Spen is same issue , also the Camera.
15/6/21 update BT SCO voice calling, IR and Samsung audio.
This built, update BT SCO driver hal to enable voice call both gsm and voip. IR is working perfectly now. Audio less plop sound or XRUN less.
Replace pre-audioprocessing with android lib -> no echo on caller side when using voip now.
27/4/21 with Samsung Audio - Initial Release
Log: Initial release with Samsung Audio , which cannot use DEEP_BUFFER_PLAYBACK so sometime you will hear plop sound and absent sound.
27/4/21 with v1a Audio Hal - Initial Release
Log: Initial release with Samsung Audio , which can use DEEP_BUFFER_PLAYBACK so sometime you will hear less plop sound and absent sound. This one gives smooth sound.
TWRP for v1a3gxx is here. Use this one to flash. This update , you can easily check+fix file patition of internal storage with this command on terminal of TWRP "chfixfs".
Please how do we get access?
kaengselllley said:
Please how do we get access?
Click to expand...
Click to collapse
Sory, I forgot to open for public. Now you can access.
khomsn said:
Sory, I forgot to open for public. Now you can access.
Click to expand...
Click to collapse
thanks
I'm getting "Error executing updater binary in zip ....."
khomsn said:
Sory, I forgot to open for public. Now you can access.
Click to expand...
Click to collapse
thanks
I'm getting "Error executing updater binary in zip ....."
Use This TWRP
i flash Viper4Android v.2.7.2.1 using magisk, is not working, and i use transparent clock & weather, it can not detect the current location, please advise.
Thanks.
khomsn said:
Use This TWRP
Click to expand...
Click to collapse
Thank you for the help
RW168 said:
i flash Viper4Android v.2.7.2.1 using magisk, is not working, and i use transparent clock & weather, it can not detect the current location, please advise.
Thanks.
Click to expand...
Click to collapse
Magisk Latest update not compatible with Viper4Android
khomsn said:
Magisk Latest update not compatible with Viper4Android
Click to expand...
Click to collapse
when use this rom [ROM][SM-P900][UNOFFICIAL] Lineage 17.1 | Android 10 Q |, viper4android works fine. its not magisk problem..
Is it possible to remove spen feature from thr rom and prevent reboot??
mvdarwin said:
Is it possible to remove spen feature from thr rom and prevent reboot??
Click to expand...
Click to collapse
mvdarwin said:
Is it possible to remove spen feature from thr rom and prevent reboot??
Click to expand...
Click to collapse
don't use spen for now
Hi Khomsn, thanks for the Rom, i flashed the new rom, but earphone using jack is not working, only working with tablet speaker, please advise, thanks.
RW168 said:
Hi Khomsn, thanks for the Rom, i flashed the new rom, but earphone using jack is not working, only working with tablet speaker, please advise, thanks.
Click to expand...
Click to collapse
Do you have previous backup for data partition, I had this problem before it is some error in data file that prevent audio route to function properly. So restore that partition and reinstall rom. Or rest to factory.
For Netflix , you have to download last version to sdcard an install. Play store not show and not allow to install.
But it works.
Hi Khomsn! First of all, thank you for the ROM and for the source codes. I have successfully build working rom using your sources.
I should notice, that for me S-Pen is working nice. First time - device indeed got frozen, and went to the reboot. But after this - no further S-Pen problems. Unfortunately, this is not working with the camera.
But, unfortunately I did not manage to get AFWall+ working. Even after adding NAT support to the kernel I am receiving errors from iptables.
ivan.odinets said:
Hi Khomsn! First of all, thank you for the ROM and for the source codes. I have successfully build working rom using your sources.
I should notice, that for me S-Pen is working nice. First time - device indeed got frozen, and went to the reboot. But after this - no further S-Pen problems. Unfortunately, this is not working with the camera.
But, unfortunately I did not manage to get AFWall+ working. Even after adding NAT support to the kernel I am receiving errors from iptables.
Click to expand...
Click to collapse
Source code is not up to date yet. Now source code is updated.
Camera error on this
libexynosv4l2: failed to ioctl: VIDIOC_QBUF (22 - Invalid argument)
libexynosv4l2: failed to ioctl: VIDIOC_REQBUFS (-1 - Invalid argument)
buf index always 0 .
Hi Khomsn, thanks for the rom. You make our note 12.2 survive through the years
One question about some notifications didn't get in previous unofficial lineage rom. This build is signed with a public key & SElinux deactivated... should I simply turn off the notification ? or any guidelines how i can resign myself the build and activate SElinux (can i use the source code to do that) ?
thank you again and the other devs for these fantastic roms