Hello ! Some days ago i started to build from source Resurrection Remix rom for Samsung Galaxy S Advance.First time when i built it,when i boot rom it give me FC at com.android.phone and Theme provider and sometimes (rarely) to dsp or systemui.Now i finished another build,which is last version of Resurrection and still same FC at boot and these FC cant be avoided,so i cant take logcat. But when i press volume keys i see popup with volume.I built correctly.
Whats the problem?FC will be gone if i delete everything related to com.android.phone,theme provider and dsp manager? @westcrip told me that he had same issues when he wanted to build for Nexus 5,also another guy got same issues after he built for other phone (don't remember model, but he didn't solve FC). Also @westcrip told me to change device sources (i cant do it because for my phone device source are provided just by a team,Team Canjica) and kernel source.Kernel can cause these FC? I'm new to building from sources, so I'm sorry for these questions. I wait for answers. Thank you !
EDIT : I deleted Dialer apk and others related to phone and theme manager,also folders,and FC at theme provider and phone was gone, BUT now first fc was at Print Spooler apk,then one at keyboard and then i got FC constantly at systemui and resurrection remix setup wizard. It's weird. Can be something wrong with permissions? I see that i get FC at apps from system/app but from priv-app too.
@Force
1) Post links to your device sources.
2) Take a look at my github and make changes according to the commit that says "initial RR bring up".
3) If you are using hdpi overlay flag in device.mk, use xhdpi.
---
The changelog of "Fix FCs of apps in i9082" that you were talking about on PM was a different issue. Only a few apps that needed to access accounts were FCing, Gmail, Email etc.
xenon92 said:
@Force
1) Post links to your device sources.
2) Take a look at my github and make changes according to the commit that says "initial RR bring up".
3) If you are using hdpi overlay flag in device.mk, use xhdpi.
---
The changelog of "Fix FCs of apps in i9082" that you were talking about on PM was a different issue. Only a few apps that needed to access accounts were FCing, Gmail, Email etc.
Click to expand...
Click to collapse
@xenon92
1) Sources:
- https://github.com/TeamCanjica/android_kernel_samsung_u8500/tree/cm-11.0
- https://github.com/TeamCanjica/android_device_samsung_janice/tree/cm-11.0
- https://github.com/TeamCanjica/android_device_samsung_u8500-common/tree/cm-11.0
- https://github.com/TeamCanjica/android_hardware_u8500/tree/cm-11.0
- https://github.com/TeamCanjica/android_vendor_samsung_u8500-common/tree/cm-11.0
Samsung Galaxy S Advance = janice .
2) I cant find it.Can you give a link please?
3) I found some device.mk,but i dont know if im in right directory.Can you tell me in which directory to look? I`m sorry for noob questions,but as i said im new to building,im still learning and i dont want to abandon this rom.
Force said:
@xenon92
1) Sources:
- https://github.com/TeamCanjica/android_kernel_samsung_u8500/tree/cm-11.0
- https://github.com/TeamCanjica/android_device_samsung_janice/tree/cm-11.0
- https://github.com/TeamCanjica/android_device_samsung_u8500-common/tree/cm-11.0
- https://github.com/TeamCanjica/android_hardware_u8500/tree/cm-11.0
- https://github.com/TeamCanjica/android_vendor_samsung_u8500-common/tree/cm-11.0
Samsung Galaxy S Advance = janice .
2) I cant find it.Can you give a link please?
3) I found some device.mk,but i dont know if im in right directory.Can you tell me in which directory to look? I`m sorry for noob questions,but as i said im new to building,im still learning and i dont want to abandon this rom.
Click to expand...
Click to collapse
https://github.com/xenon92/android_device_samsung_i9082/commits/kitkat1
https://github.com/xenon92/android_device_samsung_s2vep/commits/rr_kitkat1
If you've reached till FCs, then probably you did everything right as you said you could see the volume slider on pressing the volume keys in spite of the FCs.
janice.mk
use the flags that I have used in device_i9082.mk. Use xhdpi overlay flag and try again.
make clean, not a dirty build.
xenon92 said:
https://github.com/xenon92/android_device_samsung_i9082/commits/kitkat1
https://github.com/xenon92/android_device_samsung_s2vep/commits/rr_kitkat1
If you've reached till FCs, then probably you did everything right as you said you could see the volume slider on pressing the volume keys in spite of the FCs.
janice.mk
use the flags that I have used in device_i9082.mk. Use xhdpi overlay flag and try again.
make clean, not a dirty build.
Click to expand...
Click to collapse
im building RR for janice with @Force so , i made changes on janice.mk
http://pastebin.com/raw.php?i=VVqbQDaN
building now , tell me if that should work
Same Force Closes
@xenon92
As to me take like 5-8 hours to build, @iiD4x built with changes that you told me ( check previous post too to see modified janice.mk) and i got same FC after booting... Here is original janice.mk : https://github.com/TeamCanjica/android_device_samsung_janice/blob/cm-11.0/janice.mk
Force said:
@xenon92
As to me take like 5-8 hours to build, @iiD4x built with changes that you told me ( check previous post too to see modified janice.mk) and i got same FC after booting... Here is original janice.mk : https://github.com/TeamCanjica/android_device_samsung_janice/blob/cm-11.0/janice.mk
Click to expand...
Click to collapse
In the modified janice.mk, also add the other graphics related flags that I added in initial RR bringup commit.
I had the same issue of FCs when I first built RR for i9082, but was solved after using everything mentioned in that commit. Without the access to device it's hard to debug issues.
Anyways, now that you've compiled, add the graphics related flags to your build.prop and flash again.
Code:
ro.zygote.disable_gl_preload=true
ro.bq.gpu_to_cpu_unsupported=1
Look more into the overlays in your device tree if you still get FCs. That's all that I can suggest without access to the device and without any logs.
Good luck.
xenon92 said:
In the modified janice.mk, also add the other graphics related flags that I added in initial RR bringup commit.
I had the same issue of FCs when I first built RR for i9082, but was solved after using everything mentioned in that commit. Without the access to device it's hard to debug issues.
Anyways, now that you've compiled, add the graphics related flags to your build.prop and flash again.
Code:
ro.zygote.disable_gl_preload=true
ro.bq.gpu_to_cpu_unsupported=1
Look more into the overlays in your device tree if you still get FCs. That's all that I can suggest without access to the device and without any logs.
Good luck.
Click to expand...
Click to collapse
@xenon92
In build.prop ,these 2 lines was already there.Just ro.sygote.disable_gl_preload was 1 not true.I changed to true and flash.Result: i got same FC...
@xenon92
@xenon92 : im waiting for an answer...
Force said:
@xenon92 : im waiting for an answer...
Click to expand...
Click to collapse
You did not ask anything that I needed to answer. Read last line of my previous post.
Find a way to take logcat.
Thanks @xenon92!!
I was having FC too, but after edit janice.mk like you said it started working. Here it is: http://forum.xda-developers.com/showthread.php?t=2678695
Related
Rom info
This rom is now out of support, I have removed all download links
I am leaving the thread just for historic reasons.
Hi, I have put together aosp 4.0.4 based on the work that yjwong started.
I have created a slightly modified device tree based of CM9 device tree and
cherrypicked patches from cm9. Mostly this rom use pure aosp 4.0.4 from Google.
all my sources can be found here: https://github.com/cleaton
rom philosophy and future
I will keep a code branch as close to aosp as possible for other developers
to base their rom from if they want. For my build open to small patches
for hardware improvements/optimizations and even UI enchantments
but overall it will stay very close to aosp.
I will also and keep my building close to the way Google intended release
builds to be meaning I do proper signing with my own release-keys
odex optimization,zipaligned and so on.
Changelog
V21.04.12:
updated kernel to 3.0.28 (thanks to myfluxi)
added touchscreen patches for better sensitivity (thanks to gokhanmoral and theamhacksung)
added gps patch recently added to cm9
changed camera focus release from 3 seconds to 15 seconds
(makes it easier to focus and re-frame before taking pictures)
V04.04.12-2:
changed signing keys
added signed gapps under download to work with this rom
enabled google backup (only works with the new signed gapps)
removed su, and voice dialer
forked and using LatinIME from cyanogenmod + added dictionaries
made my sources more independent from cm to be more stable
V30.03.12:
updated to 4.0.4 release
added scene, light, macro settings to camera from teamhacksug
added video recording fix from teamhacksung
added samsungservicemode from cm9
added galaxy s2 device settings app from teamhacksung
back to using aosp toolchain for compiling
moved to latest 3.0.15 kernel from teamhacksung
gps apps now shows more satellites and connection info, patch from cm9
using opensource hw codecs (again patches from teamhacksung)
many many thanks to teamhacksung for this great progress!
V24.03.12:
Changed default wallaper
system compiled with linaro 4.6 toolchain
compiled teamhacksung experimental 3.0.25 kernel
V21.03.12:
kernel compiled from teamhacksungs source
updated to LPQ proprietary libs
mtp fixed
better working edit effects for gallery (not 100% yet)
possible new bugs introduced.
V18.03.12:
system now mounted as ro
added quick toggle menu from teamkang via aospX
press settings button in notification bar for quick toggle (long press for settings)
V10.03.12:
Compiled with arm cortex optimization flag.
Fixed assert issue with install-script.
User build instead of userdebug but modified to allow adb root.
User build gives odex optimization of system.
Fixed proper build fingerprint override to be like Samsungs.
Backup/Upgrade script from CM to get smooth upgrades.
V06.03.12:
First release.
Disclaimer
I can not leave any guarantees or support for this rom, most of all I just build this for myself.
You are on your own and you have been warned.
Install
For install instructions, radio firmware and gapps look at the
CM9 user thread found here : http://forum.xda-developers.com/showthread.php?t=1419102
Upgrade from previous version:
Same instructions as in CM9 thread
but I will add Do your own backup
if you have something important!
Clearing cache and dalvik-cache is not needed
But is probably a good habit.
(I use this rom with XXLPQ modem)
If you can't figure out how to apply those instructions for my rom this rom is not for you...
This if for Galaxy S II I9100 (International galaxys2) nothing else.
Latest release
Download: v21.04.12 -*removed*- (SHA1 7cacc6732ef05dfa7e2b3b5bec8d397787b38505 koud-AOSP-4.0.4_v21.04.12.zip)
Gapps: -*removed*- (for v04.04.12 and up)
(SHA1 ad272390b92dc4b11e36d52aaa92f01d67df5af9 gapps-ics-20120317-kaosp-signed.zip)
Old
Download: v04.04.12-2 -*removed*- (SHA1 38b6a6d189ea82b5b8cdf95223720f90747bcb37 koud-AOSP-4.0.4_v04.04.12-2.zip)
Download: v30.03.12 -*removed*- (SHA1 bf5c611abe071c9b0b1578a63ef42ddc5accb2ef koud-AOSP-4.0.4_v30.03.12.zip)
Download: v24.03.12 -*removed*- (SHA1 3230452ebdac549ccea50125f5e4fa220e561778 koud-AOSP-4.0.3_v24.03.12.zip)
Download: v21.03.12 -*removed*- (SHA1 79979bfe67e30ef52e958efdd55b11b779e6fca2 koud-AOSP-4.0.3_v21.03.12.zip)
Download: v18.03.12 -*removed*- (SHA1 d09533994bc930042f0155800ddd804da485c780 koud-AOSP-4.0.3_v18.03.12.zip)
Download: v10.03.12 -*removed*- (SHA1 7b1938025a56527ab10120947b65414c9cefe96e koud-AOSP-4.0.3_v10.03.12.zip)
Download: v06.03.12 -*removed*- (SHA1 94654ccc555585696ac17b0ddeac090d199745bd koud-AOSP-4.0.3_v06.03.12.zip)
FAQ
Q: no root?
A: yes, no root.
If you want root you can take a look at what mikk_ wrote
http://forum.xda-developers.com/showpost.php?p=24791232&postcount=169
Not working
spell correction only works for english
disable spell correction and words wont be underlined, predictive word works.
3g data does not always work on first boot after clean install
reboot and it is fine after that.
fm radio and other smaller things
(check cm9, I try and keep up to date with cm9)
Credits
Credits to teamhacksung for their incredible work providing all the necessary
patches for sgs2, and also for their help in #aospsgs2 @ freen I find some of my kernel patches.ode
Thanks to CM team, teamkang, aospX and linaro-android for their great work with android patches
Thanks to gokhanmoral and myfluxi where I get some of my kernel patches.
Thanks to haramizuki for the awesome sign/banner
Enjoy!
Hey!
Could you tell me what the bugs are?
Thx!
Great Work
any bugs ore changes on cm9 base ?
hi have any changelog? or are mismatch on CM9 ..any screenshots? ..
Thanks..
netchip said:
Hey!
Could you tell me what the bugs are?
Thx!
Click to expand...
Click to collapse
I guess this as the Sam's bug which found in CM9...
BUGS KNOWN...:
1.video recording
2.MTP storage
3.Tethering(wifi)
Sent from my GT-I9100 using Tapatalk
Good job!
Envoyé depuis mon GT-I9100 avec Tapatalk
Super Koud! Thanks for your work, I'm downloading now!
Specific for sgs2 no, not that I know of, There are a few small features missing like the ability to choose macro mode and such in camera app. But I did include patch to get full 8mpix photo. AOSP bugs are included
i suggest you put a better and mature post with all the details or this thread will be spammed by noobs
Hey, lookimng forward to this! Good job
Are you looking to strip out CM features as you get more and more stable? Similar to this?That would be incredible, good luck and I'll be testing later.
bclark said:
Hey, lookimng forward to this! Good job
Are you looking to strip out CM features as you get more and more stable? Similar to this?That would be incredible, good luck and I'll be testing later.
Click to expand...
Click to collapse
Yes, it is possible. I am thinking about including some patches from linaro (mostly performance) and if there is something I miss from CM I might try and include it. I also want to try and implement some features of my own like use menu key for multitasking. It depends on how much time I need to spend on my studies
have problems installing it
in cwm got message:
assert failed:get prop("ro.product.device") == "galaxys2" || get prop(ro.build.product") == "galaxys2"
E:Error in /sdcard/download/koud-AOSP-4.0.3_v06.03.12.zip
(Status 7)
Installation abortet
I thought there might be error during download but I downloaded it 3 times (2 directly to phone and 1 to PC)
any avdice?
I'd download it again (different pc or browser). Or turn off signature checking in cwm.
Likely a corrupt download though
Sent from my GT-I9100 using XDA App
golcheck said:
have problems installing it
in cwm got message:
assert failed:get prop("ro.product.device") == "galaxys2" || get prop(ro.build.product") == "galaxys2"
E:Error in /sdcard/download/koud-AOSP-4.0.3_v06.03.12.zip
(Status 7)
Installation abortet
I thought there might be error during download but I downloaded it 3 times (2 directly to phone and 1 to PC)
any avdice?
Click to expand...
Click to collapse
It is not an error with the download, it is a mistake in the assert generation on my part. (I must have assert check turned off when I flashed)
edit: What rom are you coming from? It looks to be a mistake in install script but at the same time I can't replicate this coming from cm7.1 or cm9 with asserts enable/disabled and signing enabled/disabled. I have included SHA1 hash sum of the update.zip in first post so you can verify that the download is not corrupt.
koudd said:
It is not an error with the download, it is a mistake in the assert generation on my part. (I must have assert check turned off when I flashed)
edit: What rom are you coming from? It looks to be a mistake in install script but at the same time I can't replicate this coming from cm7.1 or cm9 with asserts enable/disabled and signing enabled/disabled. I have included SHA1 hash sum of the update.zip in first post so you can verify that the download is not corrupt.
Click to expand...
Click to collapse
Comming from latest CheckRom. Tried disable/enable asserts and signing but with no luck. Will try download it one more time
Can anyone else confirm if the rom works? so It is not just working for me.
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
buzzboy said:
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
Click to expand...
Click to collapse
It's weird that I have to flash another rom before flashing this one....
Another cause is flashing recovery through Rom manager:
http://forum.cyanogenmod.com/topic/40120-q-status-7-installation-aborted/
Cheers
buzzboy said:
Tested and working fine.
I once had the same install error, solved by flashing cm7/9 first, rebooting, then wiping and installing again ,and the problem was solved. It's def a script that conflicts with Cm/Samsung.
Regards
Click to expand...
Click to collapse
Thanks for the info, I guess it could also be that the rom got a bad cwm installed. Flashing cm7/cm9 before installing other rom might be good habit. Wish samsung would have a real recovery partition and not a ramdisk hack...
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.)
Development suspended until (if) CM10 gets to a faster and stable state. If you want a fast, fully working new MIUI experience, check out my other ROM.
Here is an alpha release of MIUI4.1 based on CM10 for the Xperia Play. It is built upon CM10-FXP137 and MIUI Jellybean for the Nexus S.
I am using this ROM as a daily driver now and it seems to be very stable. But since CM10 is still alpha, there may be some bugs still. Future updates may also require a factory reset, so be aware of that.
A CDMA version will come soon, as soon as CM10 is confirmed working on R800x I will work on it for MIUI.
Make sure you read the blue section "Special Notes/Partially working" below before using! It contains very important existing issues and work-arounds.
Working (tested):
Calls / Text / 3G / Data
Audio
Wifi
Camera
ALS / Auto-brightness
Web Browser (from MIUI 2.8.24)
Google Play Store (fully)
Google Now (no Voice Search)
Music/Gallery/Screenshot feature (Menu+VolDown)
Location/Maps/Compass
Gamepad
Touchpads (On most games, thanks to farenheith)
If you find a game that still doesn't have working touchpads, report it in farenheith's thread. Known games reported still not working:
- Dead Space
Not working:
Torch (unknown issue)
Wifi Tether (CM10 issue)
?
Partially working/special notes:
After call is ended, audio is not routed back to loudspeaker. Sounds will be very quiet! You need to either replug headphones or reboot the phone to fix it... sadly this is a CM10 issue and I can't fix it.
In Notification Panel, the Clear/Options button in top-right corner goes off the screen. Change font-size to "Small" (in Settings > Display) to fix this for now.
Google Play Store might not show installed apps or purchased apps after signing in for the first time. Simply 'Clear Data' for Google Play Store to fix it.
When screen is off, VolUp does nothing and holding either Vol button will only skip music tracks forward
?
Download/Instructions:
Turbo MIUI v0.52.20914
(1) Download the CM10 FXP-Turbo2 kernel. You can use any other CM10 kernel if you wish.
(2) Execute following commands on PC's shell/command prompt to install kernel and prepare:
Code:
fastboot flash boot boot.img
fastboot erase system
fastboot erase userdata
(3) Copy the update ZIP to SDCard. To enter Recovery on this kernel, press Back when you feel the vibration trigger on first logo.
(4) Install the ZIP update as normal.
Screenshots:
Changelog:
Code:
v0.52.20914
-----------
- Revert: CM10-FXP137
- New: FULL TOUCHPAD SUPPORT. Thanks to farenheith!
- Fix: Camera
- Fix: SIM PIN prompt on startup (thanks to Lens_Flare). Phone is not multilingual for the moment due to APKTool bug.
- Fix: Disable Setup Wizard using old Provision, temporary until bugs sorted out in patching
- Fix: Browser user-agent
- Fix: Official Facebook app, maybe other web apps
- Fix: Magnify-glass zoom widget when selecting text (love this feature, glad I fixed it)
- Tweak: Disable services from writing adj and minfree values, allowing init.d tweaks to actually work.
v0.51.20914
-----------
- Update: CM10-FXP138
- Update: MIUI v2.9.14
- Update: Using latest MIUI browser from now on (with latest FXP webkit backend). Please report any browser crashes, video sites need testing.
- New: Multilanguage support
- New: Google Now voice search (untested)
- New: Google Now offline support (untested)
- New: Face Unlock (untested)
- Aroma: Fix "Default" install mode
- Aroma: Elite install - disable CPU rendering (set back to CPU+GPU for default). This can be switched after install by using the "Customize" option
- Aroma: Elite install - disable Setup Wizard to bypass need for Xiaomi account by using old Provision APK. May have unknown side-effects.
v0.41.20907
-----------
- Update: CM10-FXP137
- Update: MIUI v2.9.7
- Tweak: DalvikOpt flags
- Tweak: Remove entire software-rendering pathway, forcing GPU always (thanks to ShyamSasi)
- Fix: Camera
- Aroma: Added AD2SDX alpha 2 by amarullz as an sd-ext alternative, with my own CM10 fix
v0.3.20831
----------
- Update: CM10-FXP136
- Update: MIUI v2.8.31
- Fixed: No need to disable HW overlay for video anymore (Thanks to FXP)
- Removed: Bundled Live Wallpapers (except picker app)
- MIUI base switched to crespo (Nexus S)
- Using MIUI Browser v2.8.24 from now on (no new night mode, no future updates on browser)
v0.3.20817
----------
- Fixed: Play Store FC, possibly other problems due to APKTool bugs (using precompiled Framework resources, "disable signature checking" reverted)
- Update: ES File Explorer, Link2SD, Play Store and Titanium Backup
v0.2.20817
----------
- Update: CM10-FXP135
- Update: MIUI v2.8.24
- Fixed: Link2SD (permissions 777 on symlinks to fix from being stale which causes a link-break on every reboot)
- Hack: Disabled system package signature verification (required for future fixes)
- Tweak: Optimized Lowmemorykiller and VM sysctl values for better memory management and performance (for <512MB devices like ours)
- Tweak: Most system packages recompressed and zipaligned. Slightly longer boot time but saves a few precious MB on /system.
- Tweak: Disable automatic brightness
- Tweak: Moved system apps to data (default enabled in Aroma installer): Google Talk; MIUI Compass, Gallery and Music
- New: AppWidgetPicker
- New: DSP Manager (from CM10)
- New: Volume+ (skip music) mod. Sort of. While screen is off and music playing, VolUp does nothing and both keys skip forward.
- New: zRAM enabled at 10% (this is good with new snappy compression in kernel)
- New: Purgable assets enabled
- New: Kernel samepage-merging enabled
- New: Strict-mode checking disabled
- Note to self: We use libwebcore from FXP134 and WebKit core framework from MIUI v2.8.17 from now on
v0.1.20817
----------
- Initial version
- Based on official CM10-FXP134 for Zeus and MIUI UK's 2.8.17 for the Galaxy Nexus
Does this have CDMA support yet? And I assume you'd like a logcat.
game_guy said:
Does this have CDMA support yet? And I assume you'd like a logcat.
Click to expand...
Click to collapse
No, and no. Read the OP. It takes me a long time to upload.
I will release a CDMA test version soon. This will take a while because I have to upload two separate versions and I don't know if CM10 for zeusc even works yet.
Click to expand...
Click to collapse
Ah. My bad, didn't notice that sorry. >.<
It does on pax's 7/29 build. You could use that as a base for the cdma variant as that has *almost everything working.
game_guy said:
Ah. My bad, didn't notice that sorry. >.<
Click to expand...
Click to collapse
It's fine, just be patient.
cj360 said:
It does on pax's 7/29 build. You could use that as a base for the cdma variant as that has *almost everything working.
Click to expand...
Click to collapse
Link please? Is it CM10?
Upload finished.
****yeah
i'm go testing now
and will be translate russian later
this is port of that
wmaster4g said:
****yeah
i'm go testing now
and will be translate russian later
this is port of that
Click to expand...
Click to collapse
No, this is my own work. If I got it from that guy I would have given credit to him.
EDIT: He probably used my own research. Unlike most XDA "developers", I like to share what I know with the community. Or maybe he is actually one of the few skilled hackers on here and also did it himself like me.
gonna try it later after work and will report the bugs
thanks for bringing up another JB Rom pal
CosmicDan said:
It's fine, just be patient.
Link please? Is it CM10?
Upload finished.
Click to expand...
Click to collapse
Here it is and yes it's cm10.
Good work!! Goinf to have it downloaded in a few hours.. Gotta sleep first.. One question.. Does the sd card mount properly?
Sent from my Xperia Play using xda premium
cj360 said:
Here it is and yes it's cm10.
Click to expand...
Click to collapse
Alright thanks, I'll try and build a CDMA test version. But since this isn't FXP I won't be able to keep it as up-to-date.
Fat_boy555 said:
Good work!! Goinf to have it downloaded in a few hours.. Gotta sleep first.. One question.. Does the sd card mount properly?
Click to expand...
Click to collapse
Sure, why wouldn't it? Unless you mean the CM10 bug where it says "Unable to install to internal USB or memory card" when you try to install paid apps from the Play Store, no. That is a CM10 bug. But restoring everything from TB works fine, and installing free apps/updates from Play Store works fine.
CosmicDan said:
Alright thanks, I'll try and build a CDMA test version. But since this isn't FXP I won't be able to keep it as up-to-date.
Click to expand...
Click to collapse
Awesome, I know pax will update once he's able to and eventually fxp will figure out data as well.
Going kinda off-topic with this so let me know if you'd rather not discuss it here but, do you build your kernel with ics sources modified for JB or from fxp's jb sources?
cj360 said:
Awesome, I know pax will update once he's able to and eventually fxp will figure out data as well.
Going kinda off-topic with this so let me know if you'd rather not discuss it here but, do you build your kernel with ics sources modified for JB or from fxp's jb sources?
Click to expand...
Click to collapse
The kernel I'm building from is branched off JBX repo (on the 'jellybean-turbo' branch), however I did a full tree comparison and the FXP CM10 jellybean kernel is identical to the JBX one - apart from the zRAM update from FXP (Google snappy compression) which I have already merged in CM9 turbo kernel. The RAMDisk is based on FXP RAMDisk.
Computer's built, installing Ubuntu 12.04 soon so i'll be back in the game.
Cosmicdan, what does SEMCRIL look like in Framework?
Pax
paxChristos said:
Computer's built, installing Ubuntu 12.04 soon so i'll be back in the game.
Cosmicdan, what does SEMCRIL look like in Framework?
Pax
Click to expand...
Click to collapse
The full SemcRIL code for this ROM is taken directly from CM10, along with BaseCommands and PhoneFactory. It was actually a requirement to get it booting. Using my existing scripts but replacing the CM10 base for CDMA version, and the MIUI base for the CDMA Galaxy Nexus version, it should hopefully be enough....
...I would upload my "kitchen" so people can try to build it and bugtest, but how many of you guys with CDMA zeus's are good with smali? Also it requires Windows Vista/7.
paxChristos said:
Computer's built, installing Ubuntu 12.04 soon so i'll be back in the game.
Cosmicdan, what does SEMCRIL look like in Framework?
Pax
Click to expand...
Click to collapse
Good to hear! Are there any working CDMA builds floating around, or should we wait for builds from you?
Leraeniesh said:
Good to hear! Are there any working CDMA builds floating around, or should we wait for builds from you?
Click to expand...
Click to collapse
Of what? MIUI or CM10? Check the JBX thread for CM10 working CDMA. Wait, cj posted the link a few posts back to a CM10 for zeusc with working data.
Sorry to hijack cosmic,
My guess as to why CM10 data stopped working for CDMA is because of a commit done a while back (August 5th)
Now that I have a working PC i'm gonna try to undo that & see if that's the issue & if it is, I need to coordinate with FXP to create a ril for cdma & edit some common files
Pax
paxChristos said:
Sorry to hijack cosmic,
My guess as to why CM10 data stopped working for CDMA is because of a commit done a while back (August 5th)
Now that I have a working PC i'm gonna try to undo that & see if that's the issue & if it is, I need to coordinate with FXP to create a ril for cdma & edit some common files
Pax
Click to expand...
Click to collapse
That's fine, it's is still relevant since it's based on CM10. So is that build linked a while back working with CDMA fully or not? I will probably not update the GSM ROM of this until next FXP release anyway so.... yeah.
It would be good if FXP CM10 had CDMA working, because then I could easily create a patch for this GSM ROM. I really don't want to have to upload two full ROM's every time.
Since everyone's asking for a separate thread (and I want a sticky post), here's one.
BIG IMPORTANT ANNOUNCEMENT
Seriously, read this
I'm trying a thing here - discussion and all that for version 5 (and yes, there's a version 5) will be on Reddit, more specifically, here: http://www.reddit.com/r/oneplus/comments/2moqig/cm12_nonscheduled_builds_discussionupdate_thread/
This is my attempt at keeping things clean. We'll see how it goes. I won't be reading this thread.
Version 4:
Updated to Android 5.0.0_r6 across the board
Features!
Reboot, airplane mode, etc. in power menu
Hardware key rebinding
Battery percentage in statusbar
Call blacklist
Dialer lookup
Protected apps
Profiles
Kill all apps button
More?
HSPA+ also has the correct statusbar icon now
Clean build, so things will hopefully stop regressing randomly
Fixed in version 3.1:
Mobile network icon showing 3G when actually on 4G
Fixed in version 3:
Bluetooth
Some miscellaneous improvements
Fixed in version 2:
Slow boot (for real this time!)
Settings alarms causing a bootloop
Download limit exceeded, save the file to your Yandex.Disk
Also, face unlock works with new Gapps!
Fixed in version 1:
NFC
Slow boot
Enabled multi-user
Not fixed:
Keyboard crashes on swipe input (upstream, use the Play Store version)
Video recording only captures sound
More?
How to install:
Boot to recovery
Flash the latest build: https://www.androidfilehost.com/?w=files&flid=21188
Flash GApps: https://s.basketbuild.com/gapps
Flash SuperSU: http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Reboot
Full wipe before upgrading from CM11, things will go horribly wrong if you don't.
Might also need a wipe between versions, at least it didn't work right until I wiped.
DON'T flash custom kernels on this, it may or may not break horribly and you don't want to try
For developers: this is built from the latest CM12 source, here's what's different:
Removed com.qualcomm.location.apk, the new version depends on CM's MSim code which is not (yet) in L, and I can't be arsed to find an old one that works
Added overlays to enable multi-user
Last sync time: ~14:00 Moscow Standard Time, 2014-11-13
FAQ:
Q: AAAAEVERYTHINGISHORRIBLYBROKENAAAAAAAAAAAAAAAA
A: Don't flash experimental development builds if you're not expecting that.
Q: Where's Google Now Launcher?
A: It's no longer in the GApps package, install it from the Play Store.
Q: I dirty flashed this on top of a previous build and nothing/something/almost everything works.
A: Wipe data.
Q: I'm using MultiROM and ...
A: Don't use MultiROM. This is not tested for MultiROM at all. If you use MultiROM and something goes wrong, blame MultiROM.
Q: How do I enable softkeys?
A: Add qemu.hw.mainkeys=1 to your build.prop
Q: When?
A: Soon.
Important note
This is not feature complete. Please try to keep this thread clean, and don't post useless comments like "works well" or "I also have this bug". If me or some other developer needs confirmation on a specific bug, we'll ask. kthxbai
Reserved
First here ? awesome work mate.
Great !!!! :good::good::good::good::good:
Other than the bugs already listed in the OP, I'm blown away at how great these alpha builds are running. Excellent stuff, thanks for building it.
Guys, can we please keep this a development thread? I'm happy that you're happy with how it runs and all that, but please don't just post saying "me too!" - it's getting hard to filter out the signal from the noise.
Just dirty flashed with cache/dalvik wipe and it wont boot up correctly. At first black screen and sometimes the launcher choosing flashes up and after reboot cyanogenmod circle circles forever
Jility said:
Just dirty flashed with cache/dalvik wipe and it wont boot up correctly. At first black screen and sometimes the launcher choosing flashes up and after reboot cyanogenmod circle circles forever
Click to expand...
Click to collapse
Dirty flashing is the worst flashing
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
@K900 Great work with the build as well as the seperate thread. I would like to ask you if you have any plans of replacing the AOSP apps inside with their Google Alternatives in your future builds?
Daedulus Minion said:
Dirty flashing is the worst flashing
Click to expand...
Click to collapse
Thanks allot for the hard work K900!
I'm flashing this during my break.
One small bug. Location/Gps icons just doesnt want to go away from statusbar even if its fully turned off.
Sent from 0nE + 0nE aka BEAST
This is just too great! Thanks for solving the bugs (alarm and slow boot)
The rom is working great for me
Awesome
What can I say more? Fantastic work. THANK you very much indeed:good::good::good:
Google play service stopped in build 2.
inzaghi75 said:
Google play service stopped in build 2.
Click to expand...
Click to collapse
You using 11-09 gapps ?? No issues here whatsoever.
Yay, more fixes! http://review.cyanogenmod.org/#/c/77099/
Rebuilding...
fahadali2315 said:
One small bug. Location/Gps icons just doesnt want to go away from statusbar even if its fully turned off.
Sent from 0nE + 0nE aka BEAST
Click to expand...
Click to collapse
Turn off GPS and reboot
RaDiS234 said:
Turn off GPS and reboot
Click to expand...
Click to collapse
Did full wipe and flashed latest build. Its gone
Messenger crash when I want to use front camera to add selfi
netflix crashes for no reason on v1 (http://justpaste.it/hynu)
kroukes2000 said:
Messenger crash when I want to use front camera to add selfi
Click to expand...
Click to collapse
Messenger has the issue because of gapps . needs to be updated.
bobthecooldad said:
netflix crashes for no reason on v1 (http://justpaste.it/hynu)
Click to expand...
Click to collapse
Come on , its a totally different interface/coding for Android Lollipop devs for their respective apps need to update . what does that have to do with ROM ?
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?