Related
Just wanted to let you guys no that you can now go into the downloads section of ROM manager and you'll see the Sonofskywalker3 section. Blackhole is not quite ready for release yet, so you won't see it there, but I have put up a large collection of live wallpapers, multitouch keyboards from camelot, boot/shutdown animations, and launchers that you can now flash easily straight from your phone. I haven't been able to test these since i don't have a vibrant, so i'm relying on you guys. Please post any problems you have wiht anything in ROM manager to the official error reporting thread at www.androiddoes.net/sonofskywalker3 or right here in this thread and i'll try to keep on top of it. thanks for all your support guys.
Awesome! Checking it out now.
Sent from my SGH-T959 using XDA App
Dude, can you please send me instructions on how to get this added to rom manager.... I have tried koush with no luck.
Awesome you were able to!
Will this need a ROM Manager update, or is it all ready to go? (I'd look myself, but I'm flashing back from CM at the moment..)
Edit: Oh wow, is this nice. s15274n- It's under the download rom section. I know it mentions something about the premium version, click that.
to answer both questions at once: www.github.com hosts all koush's code for rom manager manifests. If you open an issue there with the code you want added one of his team will add it. once it's added you show up in rom manager instantly, no upgrade needed, because when you click donload rom in any version of rom manager it parses the code at github.com in manifests.js and looks for any vibrant = true tags, and if it finds it, it displays the info. I personally forked the manifest, edited it, and used a pull request to get it committed to the main manifest. if you want help getting yourself in rom manager, look for me in #sonofskywalker3 on irc tomorrow evening and i'll be glad to chat with you and walk you through it.
I love you...whomever the fark you are!
(Awaiting the final...mac fag sadly).
/final being tested....I hate ODIN
//no access other than work
///slashies
If it's that easy, why aren't the ROMS in there? That would save so much time and heartache.
None of the live wallpapers work for me...Axuras 2.1
Patience.....fauk, someone is going the proper route and you want to rush them.
CMR flashing FTW!
None of the live wallpapers work for me...Axuras 2.1
Give it time...an updatable rom via CWM is awesome yet time consuming....waiting patiently
Using a chihuahua to post up in this B
Hey lightninbug, do the wallpapers just not work? Did you flash them thru clockwork? Im at work and I dont want to do anything to soft brick my phone.
So you actually flash a wallpaper?? Sounds strange.... lol
yeah they dont soft brick.....just fc upon trying to open them.....yes flashed thru clockwork n rom manager...they installed to system/app..dont work tho
Thanks lightnin. I'm having trouble finding this stuff tho. My download section says it only has extras and free stuff. Not sure where to find these goodies at.
Sent from my SGH-T959 using XDA App
I'm seeing everything in the download rom section. But im on ji6 and most of the items are for 2.2 . Do i need to be running a 2.2 build fot this to work right?
Sent from my vibrant
Op 1 week ago you posted a galaxy tab Rom that bricked phones. Soon after you just recently asked devs how to make a Rom. Now your going to post a Rom. No thanks noob that's one black hole I won't be goin down.
Jerzeeloon said:
Op 1 week ago you posted a galaxy tab Rom that bricked phones. Soon after you just recently asked devs how to make a Rom. Now your going to post a Rom. No thanks noob that's one black hole I won't be goin down.
Click to expand...
Click to collapse
I'm afraid you have me confused with someone else. I have never released a ROM for galaxy tab, only one before this was the version for fascinate, and it's working great on my own phone as well as many others. Also I have never posted here asking how to make a ROM. I got started by reading tutorials online, getting help from other devs in IRC, and a lot of trial and error with my own phone before I ever released my first ROM. I don't mind criticizm, and welcome error reports, both are ways to improve the final product. However they are only helpful if they are true. If you can link me to the posts where I supposedly did these things I may better understand what you're talking about.
As far as the live wallpapers they are from the fascinate, I was hoping they would be installable without modification. Is anyone else having this issue with other roms? could you please get me a logcat during an fc so i can see what it's doing? also please try the digital rain wallpaper, it's from the market so we can use it as a kind of control group. thanks.
Sonofskywalker,
you will have to excuse the comments and tone of some in here. Recently this section has many unacceptable outbursts. I agree, issues must be raised in a constructive manner, rather than just being rude.
thanks for your work and I'll take a look.
blackerwater said:
I'm seeing everything in the download rom section. But im on ji6 and most of the items are for 2.2 . Do i need to be running a 2.2 build fot this to work right?
Sent from my vibrant
Click to expand...
Click to collapse
Actually, the bootanimations are firmware independent, so they'll work fine, the keyboards have been tested on 2.1 on the fascinate and they worked, so give them a try, and the livewallpapers came from 2.1 on the fascinate, and don't work on at least 1 2.2 rom, so if you can try them out that'd be great. and all these updates do is add an apk file to your system partition, so there's no worry of bricking as long as you have a nandroid backup.
that being said, I need a few people to test the final alpha build before i release it as a public beta, just got it uploaded this morning. Please email me at [email protected] if you're interested, and i'll be glad to send you a link. please note you'll need to have a jk6 modem and kernel installed, but i'll be glad to send you links for those too.
Q&A for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
You created two scripts?
adrianom said:
I made some scripts to clean (remove stock apps) and optimize the ROM, instead of modifying the main ROM, I created these scripts that must be run in recovery.
For download go to post 2.
...
Click to expand...
Click to collapse
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
elperroderoke said:
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
Click to expand...
Click to collapse
Yes, indeed I use some lines of your post, but to be clear, the script that is in the zip is not what is in your post, it has a lote more, and yours don't work on this device, yes a grab some delete lines to simplified the list of apps, but that was it, and I have not mentioned, simply by forgetting it.
I put the reference now:
http://forum.xda-developers.com/showpost.php?p=56221065&postcount=2
scripts
I saw the lines you included and I hope you don't mine I will use some of them to improve my script for X1068.
If you be so kind to solve a question about deleting some files I would thank you.
Is there any way to delete the updates apk in /data/app?
As you know some of them are in /system and in /data once they are updated, but the name changes if is update again.
For instance:
Books.apk is in /system but, com.google.android.apps.books-1.apk is in /data and if is updated again it will be com.google.android.apps.books-2.apk
I tried using
delete("/data/app/com.google.android.apps.books*.apk");
or
delete("/data/app/com.google.android.apps.books-*.apk");
instead of
delete("/data/app/com.google.android.apps.books-1.apk");
delete("/data/app/com.google.android.apps.books-2.apk");
bud didn't work. Is there any way to delete the files that that have similar name.
Thank you for all your work.
Regards.
Any custom rom or rom adapted for xt1069?
Error
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
xdaVTU said:
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
Click to expand...
Click to collapse
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
help
adrianom said:
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
Click to expand...
Click to collapse
Adrianom, thanks for answer my question, but yes, I made the correct download, in the name was wrote DSTV, and about the app.. I don't know what the app that I'm using, is the factory app of the device, probability of Motorola. And all the apps that has the function of camera, neither of them work with me... Thanks for everything, and.... What do you think about my english? Is good or not?
Restarts before finalizing the installation
Friend, did the procedure to install this ROM , already have the unlocked Bootloader and Flash Recovery CWM , however when are installing the phone restarts and crashes in toot screen. Has suggested to solve this?
Using scripts can usually upgrade?
If I install the Rom Stock and use the scripts before the OTA update, I can upgrade later without the applications of Motorola?
Perfect installation
Did all the installation process and everything was perfect, just a detail that installed only by CWM recovey at TWRP was not.
Root is stable? No bootloops? I turn back to kk from 5.0 because link2sd not working in 5.0 rooted and unstable root.
Not W
Its not working on me, i'm getting a black screen at boot time.
Update bootloader
If I flash this rom my bootloader will go to version 46.87?
Hi, I'll try to keep it short, between yesterday and today, I have been researching CM13, I thought it was a really hard project, but the results look promising so far, I am not ready to release anything at the moment, but I'll let you see some screenshots. This is just a side project, and I'll keep working on AOSP. I'll update this post whenever I feel like the ROM is kind of finished.
PS: This is Android 6.0.1, EMUI is just on 6.0.0 Isn't that exciting?
http://imgur.com/a/kbybk
See you!
PS2: No PMs about this please, you'll have it as soon as it's finished
CM 13 For HUAWEI P8 Lite?
I solve art/runtime error
wow this is great,i wish you all the best in these projects !
When will be this finished? I can't wait!??❤
Sent from my ALE-L21 using XDA-Developers mobile app
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
You're just awesome dude! We are all very excited about this project. This is just awesome!
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Sounds great! If you want someone who can help you testing, i can do that!
Yay, i bought p8lite 2 days ago and i love it!
Great work btw
dude this is awesome !!! so there is no more ril problem this is just great thank you very much !!!!
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Spineshankumb said:
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Click to expand...
Click to collapse
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
XePeleato said:
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
Click to expand...
Click to collapse
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
panchovix said:
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
Click to expand...
Click to collapse
Wifi worked fine on my 5.1 AOSP version, The system.img weighs roughly 800MB, I don't know exactly how much will it take, since CM13 didn't erase my internal storage.
NeedleGames said:
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, sokkoban recieved a LOT of input about his roms, there were a lot of questions and stuff, it can get really annoying, these open source projects come "As is, without warranty of any kind" - quoting the GPL so actually, trying to give some decent support on this forums is really kind.
Spineshankumb said:
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
Click to expand...
Click to collapse
The Snap app is included, however since I haven't included the camera HAL yet, I don't know for sure if it will work.
--
I'll be off like a week or so, I have compiled my own kernel, with some CPU governors to try, and I have fixed the screen DPI so far, there's still some serious patching needed.
@XePeleato yeah it worked, but if im not mistaken, with static wifi, but interesting, if the system is 800MB i think i will be fine, thanks for all about this
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Vika__ said:
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Click to expand...
Click to collapse
Sure, your opinion matters. Luckily, if I apply a patch to CM, it's also valid on AOSP, the same applies for the kernel.
XePeleato said:
Hold on I said nothing about the RIL stack, I don't know if it will work or not, but that's the last thing I am going to try to fix since I don't know if I am going to be able to fix it at all.
Click to expand...
Click to collapse
holly crap I thought this problem is finally solved :/ , okey I hope it can be fixed then , good luck !!!
Great!If I port this for Honor 4C,will it work?Sorry for my bad English.
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.
Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app
Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-
Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.
kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:
Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!