I have re-written the ICS camera HAL module to be a thin wrapper for the gingerbread libcamera.so and hence it will only work with the 2.6 kernel. The advantage is that getting to gingerbread level functionality should be quick Creating a new thread because there is a slight chance that this will work for all qualcomm devices with existing libcamera.so files (with slight mods ofcourse )
http://www.mediafire.com/download.php?wjf035mz2vzunw4
Here is a zip file which contains the new camera HAL module. README file accompanying it has instructions on the locations for the files. If you already have the previous version of camera HAL working, all you have to do is replace camera.qsd8k.so and libcamera.so with the ones in the zip file.
What works:
1) Preview works.
2) Taking a picture works pretty well.
3) Size of picture is no longer huge.
4) Software zoom works.
5) Most of the other knobs like focus, file size etc. seemed to work as well in my testing.
6) Pretty stable as far as I can see
Not working yet:
Video and other fancy stuff.
If people have requests for other qualcomm devices after having tried the HAL included in the zip file, kindly include the following information.
1) logcat from having used the HAL module.
2) build.prop
3) libcamera.so from gingerbread ROM for the device.
4) liboemcamera.so from gingerbread ROM.
Currently known to work on the following devices:
1) Nexus One.
2) HTC Desire
3) HTC HD2
Enjoy and thanks for all the feedback.
Updates:
02/09/2012
Working barcode scanner mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?w4fu0u05qtxq3tu
01/30/2012
Working Panorama mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?5r599m5jg5yfaqn
Known issues:
Sometimes screen has some garbage while in Panorama mode viewfinder. Quitting completely from the app and restart or invoking Gallery from inside the app and returning back to camera app should mostly fix it.
Video enabled version:
Fastboot compatible images compiled from evervolv base:
For Stock hboot :
http://www.mediafire.com/?wdlip7h6necetia
For HBoot(s) supporting larger /system partition
http://www.mediafire.com/?f6rz3sz2r97qln0
Source code is now available at
https://github.com/rapmv78/
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
please show me what i have to type in adb to push these files? (sorry i'm noob)
is camera.qsd8k.so not included?
sorry for my english..
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
One step closer!
Thank you!
twistedumbrella said:
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
Click to expand...
Click to collapse
Link fixed. The files included in the zip are the ones to be used. The generic libs part is only for people with non nexus one devices and would want help enabling camera on them. Hope this clarifies better.
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
rapmv78 said:
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
Click to expand...
Click to collapse
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
mulerokeh said:
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
Click to expand...
Click to collapse
If you have previously working camera, you can skip flashing the boot-new.img file. It is there for people who do not have existing ics camera hal. Rest looks fine to me.
twistedumbrella said:
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Maybe you should ask @charnsingh_online help for video, as he already works on 720p for N1
rapmv78 said:
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Click to expand...
Click to collapse
So what were the kernel changes?
twistedumbrella said:
So what were the kernel changes?
Click to expand...
Click to collapse
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
rapmv78 said:
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
Click to expand...
Click to collapse
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
twistedumbrella said:
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
Click to expand...
Click to collapse
The hal code itself is generic, but it depends on libcamera.so, which inturn depends on kernel structs and constants to match the running kernel for successful control ioctls/pmem etc.
Can confirm this works on HTC Desire exactly as mentioned in OP.
Sent from my HTC Desire using XDA App
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
it works for me, but sometimes not responding after take 2 or 3 photos..
but great work!!
Sent from my Nexus One using xda premium
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
Works both fine with texasice ICS!
Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
This is a kernel module that defeats HTC's system write protection
Devs are free to use this in their ROMs, just credit me and link here
Download:
Kernel version 3.0.21-g6c11713: http://goo.gl/u39km
Kernel version 3.0.21-gfdb1a80: http://goo.gl/5hRmU
Click to expand...
Click to collapse
How to use:
copy the module to your device (eg: /system/lib/modules), insert the module, then remount system
insmod /system/lib/modules/wp_mod2.ko
mount -o remount,rw /system
This must be done at boot, if you make changes to /system, then load the module, you risk corrupting the filesystem.
How to implement in ROMs
There are two good ways to implement this in ROMs:
1. make an init.d script containing the commands above
or
2. add the commands to init.rc in the ramdisk
NOTE TO POTENTIAL KERNEL DEVS:
The module would not be necessary if you make a custom kernel. Simply make sure it is compiled without CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
Please hit the Thanks button if you download this
If you really like it, please consider buying me a beer
Source code: http://goo.gl/VmSwe
This is a great news...
I think most people is using kernel version 3.0.21-g6c11713
as this comes with the EU & Asia ROM.
It will only work for the exact kernel version, and even then it may take many attempts before I get it right.
Here's one for kernel version 3.0.21-g6c11713
download: http://goo.gl/Vtcex
Please let me know exactly what happens after running the commands in the OP
Warning: don't go trying this unless you know what you're doing, it probably won't work yet and it might crash your device
flar2 said:
It will only work for the exact kernel version, and even then it may take many attempts before I get it right.
Here's one for kernel version 3.0.21-g6c11713
download: http://goo.gl/Vtcex
Please let me know exactly what happens after running the commands in the OP
Warning: don't go trying this unless you know what you're doing, it probably won't work yet
Click to expand...
Click to collapse
I just change the version no to the earlier wp_mod2.ko and tested, it works
I can delete a file and after reboot the deleted file is not returning
Testing your new wp_mod2.ko and will let you know in a while
EDIT:
Yeah...Whoa... tested the new wp_mod2.ko and ...yippieeee... IT WORKS
Attached are the screenshot before and after I removed 3 items
Thanks a lot
So I guess the best is to edit the ramdisk to run this module ?
Or an init.d script will be enough ?
Sorry for a noobish question.
And request for permission to include this in my ROM... thanks
ckpv5 said:
I just change the version no to the earlier wp_mod2.ko and tested, it works
I can delete a file and after reboot the deleted file is not returning
Testing your new wp_mod2.ko and will let you know in a while
EDIT:
Yeah...Whoa... tested the new wp_mod2.ko and ...yippieeee... IT WORKS
Attached are the screenshot before and after I removed 3 items
Thanks a lot
Click to expand...
Click to collapse
Great! Thanks for testing.
I'll update the OP.
While I'm at this are there any other kernel versions in use?
ckpv5 said:
So I guess the best is to edit the ramdisk to run this module ?
Or an init.d script will be enough ?
Sorry for a noobish question.
And request for permission to include this in my ROM... thanks
Click to expand...
Click to collapse
Either way will work fine
Anyway, you're no noob, I used your ROMs back when I had a One V, top notch stuff!
flar2 said:
Either way will work fine
Click to expand...
Click to collapse
Yep.. confirm either way works fine.
Thanks again for this great mod
flar2 said:
This is a kernel module that defeats HTC's system write protection
Devs are free to use this in their ROMs, just credit me and link here
How to use:
copy the module to your device (eg: /system/lib/modules), insert the module, then remount system
insmod /system/lib/modules/wp_mod2.ko
mount -o remount,rw /system
This must be done at boot, if you make changes to /system, then load the module, you risk corrupting the filesystem.
How to implement in ROMs
There are two good ways to implement this in ROMs:
1. make an init.d script containing the commands above
or
2. add the commands to init.rc in the ramdisk
NOTE TO POTENTIAL KERNEL DEVS:
The module would not be necessary if you make a custom kernel. Simply make sure it is compiled without CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
Source code: http://goo.gl/VmSwe
Click to expand...
Click to collapse
Thank you so much for making this.
Yes, yes, yes!!
Finally i can remove sh*t and integrate updates into system with link2sd on my desire x
thanks man!
@ckpv5
thanks for the addon you made for your mysense-rom
Thanks man, looks great.
I'll add this in Half~Sense V 0.8
Sent from my awesome fridge
Added to Index, a very usefull tool.
It works, added it as an init.d script.
Adding in V.0.8
Hi,
can anyone made a flashable ZIP for users who has already installed some ROMs on HTC Desire X please ?
thanks, Petr
monopoly said:
Hi,
can anyone made a flashable ZIP for users who has already installed some ROMs on HTC Desire X please ?
thanks, Petr
Click to expand...
Click to collapse
cpkv5 made some zip for mySense: Link. It's working for me.
Hi flar2
Any chance a mod for 3.0.21-g01fle38 ?
I tried and it works fine for me and most users but today one user mentioned my edited wp_mod2.ko not working.
so maybe you can help with a proper one ?
thanks in advance.
ckpv5 said:
Hi flar2
Any chance a mod for 3.0.21-g01fle38 ?
I tried and it works fine for me and most users but today one user mentioned my edited wp_mod2.ko not working.
so maybe you can help with a proper one ?
thanks in advance.
Click to expand...
Click to collapse
I'm going to try to install your version and see if I can change the CID permanently (or delete the apps permanently too). I have flashed the OC kernel from atis112 so I guess I don't need to flash yours too, right?
Thanks flar2 for your work!
gbueno6 said:
I'm going to try to install your version and see if I can change the CID permanently (or delete the apps permanently too). I have flashed the OC kernel from atis112 so I guess I don't need to flash yours too, right?
Thanks flar2 for your work!
Click to expand...
Click to collapse
You CAN''T change CID without S-OFF.
Stereo8 said:
You CAN''T change CID without S-OFF.
Click to expand...
Click to collapse
I know, but I saw some topics regarding change CID with S-ON in One S so I just wanted to try (with no luck).
Well, I really want to S-OFF so I can flash kernels from recovery...
Sent from my HTC branded muffin...
Hi!
As I couldn't find any simple torch that could handle burning_led mode provided by some u8500 kernels I hacked existing torch app. And since I don't have a working Android build tree I just decompiled existing one. I don't know if it will work on other cm roms, I'm not even sure if it'll work on a different build of Vanir, because I don't know how tightly apps are tied to a particular version of framework-res.apk.
I just needed it, it works for me and if anyone else finds it useful then great, but it's given 'as is'.
APK on mediafire
GIthub repo
It requires additional file permissions on sysfs to work:
chmod 666 /sys/class/camera/flash/rear_flash
chmod 666 /sys/class/camera/flash/burning_led
init.d script
mkaluza said:
Hi!
As I couldn't find any simple torch that could handle burning_led mode provided by some u8500 kernels I hacked existing torch app. And since I don't have a working Android build tree I just decompiled existing one. I don't know if it will work on other cm roms, I'm not even sure if it'll work on a different build of Vanir, because I don't know how tightly apps are tied to a particular version of framework-res.apk.
I just needed it, it works for me and if anyone else finds it useful then great, but it's given 'as is'.
APK on mediafire
GIthub repo
Click to expand...
Click to collapse
On which rom have u tested this modified apk?
pictorul20 said:
On which rom have u tested this modified apk?
Click to expand...
Click to collapse
Vanir nightly 4.4.4.111914
If it didn't work for you it's probably due to missing file permissions I forgot to mention - added them and init.d script to post #1
Sorry for the problem
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before(you can do it after flash,but recommended before) installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
v2 - SELinux fix.
Download: Google Drive
Sources: Google Drive
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
Flash kernel in odin.
This is my first kernel which I create on Linux. I hope everything will be working stable.
Download: Google Drive
Click to expand...
Click to collapse
Thank you - I flashed it as per your instructions. Seems to have worked fine and it's showing it as running as permissive!
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Alan-B said:
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Click to expand...
Click to collapse
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Blue cat said:
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Click to expand...
Click to collapse
Hi,
With my boot.img I have no this message! It is when I made out a will your that and come this message!
NB:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Alan-B said:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Click to expand...
Click to collapse
Ok,I found a solution.
You need to remove SecurityLogAgent
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
karthikrr said:
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
Click to expand...
Click to collapse
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Blue cat said:
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Click to expand...
Click to collapse
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
karthikrr said:
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
Click to expand...
Click to collapse
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Blue cat said:
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Click to expand...
Click to collapse
Brilliant! Thanks for sharing ... As and when I learn anything relevant to the issue of P605 vs. P607T, will update here.
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
valexi said:
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
Click to expand...
Click to collapse
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
Click to expand...
Click to collapse
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
karthikrr said:
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
Click to expand...
Click to collapse
I tried this. With ro.securestorage.support false. Still no WiFi passwords saved after reboot.
Other than that, this works great!
Xposed (for Samsung by wanam) works great!
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
BlueCat, I went ahead and compared checksums for the stock p607t and p605 kernels, they do NOT match. I also extracted the kernels themselves and the zimage files are of different sizes. I then compared the default config files of the P605_LL_EUR source with the only available source for the P607T, which is KK ... They are considerably different. I am of course going with the assumption that the core config for the kernel between KK and LL should not be TOO different, but of course, this is NOT a reliable test. Lastly, I should also say, the P607T source contained an insane number of config files in the Arch/Arm/configs folder, while the P605 source only had three files! I only compared the three that were common ... It seemed like the 607T has the config files for every possible version of the device, while the 605 one had very specific configs for that device only ... This I am speculating based on the fact that the 607T folder even had a msm8894_sec_l03ltmo_defconfig file in addition to the msm8894_sec_l03leur_defconfig file in the 605.
Will do more comparisons over the next few days, but it does seem like there are more changes under the hood between the 605 and the 607T than one would expect. I really wish samsung would release the source for the 607t, but if you check that page, there is just one single KK code there and nothing else, so it does not seem likely anytime soon
Blue cat said:
Ok,I found a solution.
You need to remove SecurityLogAgent
Click to expand...
Click to collapse
Re,
Ok remove SecurityLogAgent and folder Container it is ok...
But delete all other knox and Klm gives a problem with the playstor. (Certain protections cannot be erased)
Hey guys,
Great news around, especially with roms like Alan-B's. Thanks for sharing :good:.
Running 4.4, planning to update 5.x as soon as I'm sure I can run Linux Deploy (meaning the need of permissive kernel), though I can't find any intel about VTS (Virtual Terminal Support) enabled kernel. I've been looking for months a way to run framebuffered distros and looks like this is the solution.
I could try to make it myself but I have no experience in kernels, would someone mind give me a hand to get to this goal? At least give me a hint to "quickly" develop and try one, to see if it works and how well...
Don't even know if I'm looking the right way anymore, so thanks by advance for any help and again for the sharing :highfive:.
karthikrr said:
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
Click to expand...
Click to collapse
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
valexi said:
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
Click to expand...
Click to collapse
You can't. Reflash, root, edit build.prop, reboot, set wifi password once again, reboot, it SHOULD be fine. If its not after this sequence, Im not sure what else may work. Every case of this particular problem that I've seen was resolved with this solution.
Luckily I didn't reflash yet. I checked again build.prop and securestorage was true. For some reason it didn't stick first time.
I edited it again and now WiFi works as intended. So I can say that this solution works. Great kernel.
Sent from my ONE A2003 using Tapatalk