[ROM] (21/5/12) Renaissance for YP-G1 V3.0 (FINAL) - Samsung Galaxy Player 4.0, 5.0

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.)

Related

[RC][PORT][CDMA] Team Gummy - Update:20120523

UPDATE: With the newest release (05/23), Root is broken, flash superuser 3.0.7 to fix.
UPDATE 2: Working on a flashable zip so GSM users can use Gummy, too.
UPDATE 3: Current release has broken Google Play, I am looking into fixing it.
NOTE: IF YOUR PHONE FORCE-CRASHES ON BOOT, YOU DID NOT FOLLOW THE DIRECTIONS FOR INSTALLATION. READ THEM. UNDERSTAND THEM. THEN INSTALL. IF YOU DO NOT FOLLOW THEM I WILL LAUGH AT YOU.
I did not do ANY of the major work for this ROM. All I did was get the correct build environment so Qcom chips would work. All credit for this rom goes to the Team Gummy Devs below.
Team Gummy:
Kejar31 - Primary Developer and Project lead
Syaoran12 - Developer
Mobile_Sensei -Developer
Atesc - Developer
Sixstringsg - Developer
Stevespear426 - Developer
PoiTEE - Forum support guru
Daank - Wallpapers and artwork
Credits for help getting this to work:
Hashcode - Thanks for the pm help & who I also kanged the intro from
Atarii - Pointers on irc!
Keiran & Doom - For awesome Kernels!
FXP - For device & vendor trees (that I modified) & giving us CM9 in the first place to play around with!
Everybody's whose worked on AOSP/CM9 sources!
Source Code for my tweaks:
vendor/Gummy (adding in zeus)
vendor/semc (changing libs to R800x instead of R800i)
device/semc/msm7x30 (small changes)
device/semc/zeus (small changes to make it work)
frameworks/base (Latest cm9 code integrated into gummy framework)
How To Install:
Code:
1) Download Doomkernel for ICS (download link below)
2) Flash DoomKernel (you’ll need it for install, but nothing else)
3) Boot into recovery (back button when your phone vibrates & led turns on)
4) Wipe Cache/Davlik Cache.
5) Optional: Wipe Data
6) Install Gummy Zip
7) Optional: Instal latest Gapps
8) Open up terminal/command prompt
9) When Install is done, go to mounts & storage and mount both /cache & /data
10) Type into command prompt/terminal adb shell
11) copy/ paste the folowing 2 commands into the shell
If you didn’t wipe data:
mv /data/dalvik-cache /cache/davlik-cache
ln -s /cache/dalvik-cache /data/dalvik-cache
If you did wipe data:
mkdir /cache/dalvik-cache
ln -s /cache/dalvik-cache /data/dalvik-cache
12) The first command takes about a minute.
13) Turn off phone, flash included (DFK-v4 kernel)
14) Turn on & enjoy Gummy
Sources:
Davlik cache fix: (Courtosy of Reukiodo) http://forum.xda-developers.com/showpost.php?p=7562614&postcount=2 (slightly modified to work for us)
Downloads:
Gummy: http://www.mediafire.com/?iz5gnorkpbgfk
Doomlord ICS v2: http://www.mediafire.com/?66mf9jw7c5vuxz6
Current Bugs:
Wifi hotspot tethering does not work
Panoramic Camera
Video Recording
Bluetooth A2DP
Facebook Sync (it's a facebook issue, not a framework issue)
Kernels you can use:
KeiCS KernelSource
DoomLord's ICS Beta -- Source -!- Breaks hardware video
Google Apps: (needs to be flashed separately)
http://goo.im/gapps
Changelog
2012 May 17th -- Beta Release
2012 May 23rd -- Full Release!! Graphical Glitches Fixed!! Note: For this release, I did not include a kernel, either download KeiCS or Doom (links above)
Screenshots
Reserved for more info
Sent from my R800x using Tapatalk 2
Reserved.
Sent from my R800x using Tapatalk 2
I'll update the firmware list. I wont like it because I don't know if the thread number will change. I've been an admin on many forums and haven't noticed it.
Sent from my R800x using XDA
Yay, I just got my Xperia and I'm loving it. I love Gummy on my Nexus, and I bet it will be just as good on the Play.
Release coming very soon, need to work out kernel difficulties. (took down the bad zip)
paxChristos said:
Just a heads up, I'm uploading an unstable version of gummy if anybody wants to tear it apart,
WARNING: THIS VERSION DID NOT BOOT FOR ME, IF SOMEBODY WANTS TO TRY & FIGURE OUT WHATS GOING ON, TRY IT.
Once again: IT DIDN'T BOOT FOR ME, MAKE A NANDROID BEFORE YOU FLASH IT, IT PROBABLY WON'T BOOT FOR YOU EITHER!!!
(link to folder: http://www.mediafire.com/?iz5gnorkpbgfk )
Click to expand...
Click to collapse
I'm going to take a look through and see what, if anything, I can try to figure out. Is it based on CM9 like CNA is, or did you try to do a direct port?
Update: Well, after digging through the zip, I noticed there were a lot of things missing in the /system/framework and the /system/bin folders. In my noobish logic, I figured if the rom is based on CM9 stuff, why not copy/paste the "missing" stuff from CM9? And after trying that, I didn't make it past the kernel splash screen. In my limited experience, I don't know what to do to help.
lightningdude said:
Update: Well, after digging through the zip, I noticed there were a lot of things missing in the /system/framework and the /system/bin folders.
Click to expand...
Click to collapse
Depending on the kernel, /system/bin could be filled out other ways. but thanks for looking in /system/framework, that's where (I think) the problem is!
Pax
paxChristos said:
Depending on the kernel, /system/bin could be filled out other ways. but thanks for looking in /system/framework, that's where (I think) the problem is!
Pax
Click to expand...
Click to collapse
I know it's been less than a day, but have you had any chance to pick at it and figure anything out? I'll most likely be sticking with CNA rather than switching to Gummy, but if there's anything I can help with, let me know.
lightningdude said:
I know it's been less than a day, but have you had any chance to pick at it and figure anything out? I'll most likely be sticking with CNA rather than switching to Gummy, but if there's anything I can help with, let me know.
Click to expand...
Click to collapse
Still working on it
Got it.
Waiting on Team Gummy's Ok to post.
The problem was deeper than the framework? Or did life catch up to you?
Sent from my R800x using XDA
lightningdude said:
The problem was deeper than the framework? Or did life catch up to you?
Sent from my R800x using XDA
Click to expand...
Click to collapse
Nope, needed to take a different tact in building & got it built uploading soon
It may be obvious by the need for step-by-step instructions, but this is not for the faint of heart.
That being said, this rom definitely has great potential, the main thing holding me back is the graphical issues. It sounds like pax already knows where to look, it's just a matter of making it right. The other thing keeping me from Gummy is the fact that I've finally gotten settled into PlayOSP, and I'd kind of like to stay on a rom for more than a few days for once.
I can't believe I'm making a comment about having too many options! Just a month ago, I was stuck with almost two ICS roms, and now we're over four! And two of them are still just for us CDMA users! Life is good. Thanks, paxChristos.
Working on a possible fix for graphics now, will update if it works
Pax
Sweetness
My fix didn't work (i edited one too many files) I'm gonna have to go back & take is slowly (still working on it, it's just gonna take a little while )
Pax
Take your time, man, you've done a lot already.
Sent from my R800x using XDA
Release Candidate Relased for Team Gummy Rom!! Everything that works in CM9 should work with Team Gummy!!
Pax
paxChristos said:
Release Candidate Relased for Team Gummy Rom!! Everything that works in CM9 should work with Team Gummy!!
Pax
Click to expand...
Click to collapse
Great work pax!

[DEV][WiP] ramdisk-hijack - load custom ramdisk [4.3]

Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m

(ROM)(AOSP)Lollipop AOSP

This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://www.androidfilehost.com/?fid=95784891001615065
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Thanks!
papi92 said:
This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://docs.google.com/a/droid-hive.com/file/d/0B0yE3jDMsld7dWZPck5sRXU1T28/edit?usp=docslist_api
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Click to expand...
Click to collapse
Your download is permission-only, FYI.
Let me change it
https://www.androidfilehost.com/?fid=95784891001615065
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
I ran a build myself. Haven't had the chance to see what may be missing. Would you mind sharing the fix for recovery being overwritten?
papi92 said:
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
Click to expand...
Click to collapse
Encryption enabled by default?
Yes. And Milly7 its in BoardConfig.mk I can do it later today.
Added an androidfilehost link.
This may be a dumb question but how different is this from the stock lolipop on the Nexus 6? I've used AOSP before but it's been a while.
You'll lose all the proprietary google apps as the default options. But you can download them from the play store. I am noticing a huge difference in performance tho. I'm hoping to fix the video playback soon. I want to just add a battery percentage option tho then I'll just optimize without touching hardware or kernel.
Would someone mind uploading the gallery.apk from this build? Currently using an older one which force closes on the editor screen and don't want to backup->flash->pull apk->restore.
Thanks for this papi92. I compared the vendor folder from the stock image to aosp and it appears quite a few files are missing. I really don't know how to add them and have always relied on devs such as yourself. Can upload the stock vendor folder if you need it.
That'd help a lot but those won't be the only ones missing. Some go in weird spots. I just need the missing ones.
Here is my vendor file for anyone who can help https://github.com/papi92/android_vendor
...and it begins. Thanks OP!
Here are the vendor files from the stock image. http://d-h.st/XV7
I was looking at them on 2 different computers so it was hard to tell which were different, but there are quite a few missing.
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
papi92 said:
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
Click to expand...
Click to collapse
Congrats on your newly born and thanks for your work.
I pooped my pants once, it's a long story....

[TOOLS][KERNELS]Ultimate AIO compilation thread for cancro

Some flashable zips. Most are made by me (by modifying other zips; I'm no expert at scripting yet)
If the zip is my creation, you'll find a 'Credits' file with- you guessed that right- credits. Open it as text.
For the zips that are NOT made by me, I have tried to give proper credits. If I've forgotten to mention someone, PM me.
Repartition cancro:
See THIS THREAD.
All credits to @arif920629 for the guide, and @audahadi and @eaXier for the zips. I have just mirrored them.
Repartition to 1.2GB Single System
Repartition to Stock Layout
Fonts:
See this awesome thread by @gianton
http://forum.xda-developers.com/android/themes/fonts-flashable-zips-t2964304
Bootanimations:
Check out this awesome website/app by Paul Price (eth0):
Website- http://www.bhoot.co.uk/
App- https://play.google.com/store/apps/details?id=uk.co.bhoot
Community- Google+
Enable Navbar/Softkeys:
LINK
Note: This will edit your build.prop file (/system/build.prop) and will probably break OTA updates for ROMs with incremental OTAs (e.g. Mokee).
Note2: AFAIK, OpenDelta OTAs will NOT break in Resurrection Remix for example (because I OTA'd my way through Omni for almost 6 months on my old GT-N7000 with navbar enabled manually). If it does, please inform.
CameraNext Flashable:
Flashable zip for the CameraNext AKA CyanogenMod Camera AKA OPO Camera
I have found this camera app to be fully functional (tested on AOSP 5.0.2 by Ivan and XenonHD by @audahadi) if you tweak the settings.
Tweaks:
-If you get a black screen or a static image with just camera controls visible, in settings set Viewfinder mode to 'Letterbox'
-If video recording FCs or don't get saved, try setting resolution for video to 720p or lower. (Note that video FCs may also be due to kernel issues especially in the newer source-built kernels)
Ivan's kernel (possible fix for call bug):
NOTE: This will fix mobile data, WiFi and video playback errors common in ROMs which have source-built kernel by flashing kernels from Ivan's AOSP builds and placing reqd lib files.
It should also eliminate the new screen off death (call bug v2), please report if you get call bug with Ivan's kernel.
BUGS:
-Stock FM Radio app doesn't work anymore (5.0.2 ONLY?). More files from Ivan's need to be transferred probably...
Note: @audahadi and @Bitti09 are working hard on the kernel sources. If you want to help them out then I'd suggest NOT flashing these on their CM12/12.1 builds...test their work and give proper feedback.
For Android 5.0.2 ROMs
Credits:
- Ivan for kernel
- @audahadi: the required files were taken from his XenonHD ROM
- @SkipperRyujin for figuring out the WiFi fix
- Me, for all the download ROMs, backup, copy, paste, restore, unzip, modify script, rezip, testing. Took the better part of an afternoon.
For Android 5.1 ROMs
(NOTE: Below is an updated zip with the source-built kernel and modules from @audahadi's latest XenonHD 5.1 build, as he has managed to fix almost everything major: WiFi, Data, Camera, FM Radio. Long live @audahadi!)
Credits:
- Ivan for kernel
- @SkipperRyujin for figuring out the WiFi fix and providing the required files.
- Me, for all the download ROMs, backup, copy, paste, restore, unzip, modify script, rezip, testing. Took the better part of an afternoon.
For Android 5.1.1 ROMs
Credits:
- Ivan for kernel
- @ZenR2 for providing required files.
- Me, for all the download ROMs, backup, copy, paste, restore, unzip, modify script, rezip, testing. Took the better part of an afternoon.
@audahadi's kernel w/ WiFi fix:
NOTE: This will fix mobile data, WiFi and video playback errors common in ROMs which have source-built kernel by flashing kernel from audahadi's XenonHD 5.1 build and placing reqd lib files.
BUGS:
-You tell me (on XenonHD everything works)
Audahadi's kernel for 5.1
(Untested; my phone is not with me now. This was made from the zip above by replacing the files. Shouldn't brick your phone. :silly
Credits:
- @audahadi for the kernel and all the help.
- @domeniko260 for providing the reqd files.
Stuxnet+ kernel:
This is a custom kernel by @Gnome.
Downloads, features, updates:
Official Stuxnet+ kernel thread by @Gnome
Credits:
- @Gnome for the kernel. It is entirely his work.
Darkness kernel:
This is a custom kernel by HTCMania user alexret. See original thread for feature list, compatibilty and latest updates.
ORIGINAL THREAD
Downloads, features, updates:
Official Alex Kernel XDA thread by @alexret
NOTE: If you flash the CM12.1 version and WiFi doesn't work for you, flash the second one, it includes the kernel modules for WiFi.
Credits:
- @alexret for the kernel. It is entirely his work (based on audahadi and bitti sources).
StellAR kernel:
This is a custom kernel by @arnabbiswasalsodeep.
Downloads, features, updates:
Official StellAR kernel XDA thread by @arnabbiswasalsodeep
Credits:
- @arnabbiswasalsodeep for the kernel. It is entirely his work (based on audahadi and bitti sources).
Good ... but:
repartition - why only 16 gb version? I have 64gb and repartition worked ...
please repare share gdrive links options - it wrote "need permission"
thanks.
MTK6589 said:
Good ... but:
repartition - why only 16 gb version? I have 64gb and repartition worked ...
please repare share gdrive links options - it wrote "need permission"
thanks.
Click to expand...
Click to collapse
Oh, I thought the partition layout was specific to 16GB variant, didn't want any noobs bricking their device.
If it worked for you, I'll remove that warning.
And I''ll change permissions too, thanks!
EDIT: Links working?
The Dork Knight Rises said:
Oh, I thought the partition layout was specific to 16GB variant, didn't want any noobs bricking their device.
If it worked for you, I'll remove that warning.
And I''ll change permissions too, thanks!
EDIT: Links working?
Click to expand...
Click to collapse
links works fine ...
waiting for 5.1 version
thanks for your work.
MTK6589 said:
links works fine ...
waiting for 5.1 version
thanks for your work.
Click to expand...
Click to collapse
5.1 version up. Note that I haven't tested it.
But it uses the exact same script (just different file, from Ivan's 5.1 build) as the 5.0.2 one (which I've tested to be working) so it shouldn't screw up your phone. Just keep a backup first. Just in case.
If you do flash it, and everything works, please report.
How's the battery life?
Great.. Information gathered at one place is always easy for all. Hope u keep it updated..
Some flashlable zip for vibration reduction?
Is back to stock repartition gives the ota update support for miui..?
As someone comment like he no longer getting update when he change partition layout to 1.2 GB and then back to stock with this zip.
Flitz01 said:
How's the battery life?
Click to expand...
Click to collapse
On what? These are just mods and tools. Battery life will depend on your ROM and apps installed etc...
Nyqi said:
Some flashlable zip for vibration reduction?
Click to expand...
Click to collapse
I don't think that's possible. But I'll search around a bit.
Cancro90 said:
Is back to stock repartition gives the ota update support for miui..?
As someone comment like he no longer getting update when he change partition layout to 1.2 GB and then back to stock with this zip.
Click to expand...
Click to collapse
I believe @eaXier made a zip based on audahadi's which allows OTAs and MiFlash too (by changing the units to bytes or something)...
I mirrored that one now. :good:
The Dork Knight Rises said:
On what? These are just mods and tools. Battery life will depend on your ROM and apps installed etc...
Oh sorry, i meant Resurection REmix with Ivan kernel
Click to expand...
Click to collapse
Kernel with Wi-Fi for 5.1 on RR 5.4.1 no deep sleep (
pgqta said:
Kernel with Wi-Fi for 5.1 on RR 5.4.1 no deep sleep (
Click to expand...
Click to collapse
Did you turn off 'Keep Awake' for Google Play Services??
Could you check what's keeping a Wakelock?
The Dork Knight Rises said:
Did you turn off 'Keep Awake' for Google Play Services??
Could you check what's keeping a Wakelock?
Click to expand...
Click to collapse
WLD show me that com.ck.services used 128 times in alarm wakeup, but in cpu wakeup everything is good. Where I can find keep awake? Sorry for my poor english
pgqta said:
WLD show me that com.ck.services used 128 times in alarm wakeup, but in cpu wakeup everything is good. Where I can find keep awake? Sorry for my poor english
Click to expand...
Click to collapse
In Settings>Privacy>Privacy Guard>Advanced, you can manage permissions for each app.
Find the ones which are keeping unnecessary wakelocks and uncheck the 'Keep Awake' and 'Wake up' permissions.
Note that disabling 'Wake up' for apps such as GMail/WhatsApp for example will prevent the app from waking up from time to time to sync hence delaying notifications.
PS. Your English is pretty good! :good:
The Dork Knight Rises said:
In Settings>Privacy>Privacy Guard>Advanced, you can manage permissions for each app.
Find the ones which are keeping unnecessary wakelocks and uncheck the 'Keep Awake' and 'Wake up' permissions.
Note that disabling 'Wake up' for apps such as GMail/WhatsApp for example will prevent the app from waking up from time to time to sync hence delaying notifications.
PS. Your English is pretty good! :good:
Click to expand...
Click to collapse
Thanks, it's working!)
So the repartition back to stock layout on the op is the one that updated & allows OTAs, MiFlash??
damnthomas said:
So the repartition back to stock layout on the op is the one that updated & allows OTAs, MiFlash??
Click to expand...
Click to collapse
yes
Audahadi's 5.1 kernel with fixes uploaded!
If you flash it, please give feedback.
The Dork Knight Rises said:
Audahadi's 5.1 kernel with fixes uploaded!
If you flash it, please give feedback.
Click to expand...
Click to collapse
Why you don't post alexkernel v3?

[Kernel][5.1.1][P605] Stock SELinux Permissive kernel (OI5)

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

Categories

Resources