The project is based on Cyanogenmod 12.1.
At the moment, compiled alpha version of the firmware 12.1 CM + NPROJ.
Place it just after you make a backup of all data.
What is now present in the firmware:
Driver stock camera, no differences photos from photos taken at the drain, everything works, panorama, skype, etc. The runoff when you press the shutter release triggers auto-focus, so now it is 12.1 CM!
New initlogo.
I actually Russian, and accordingly made Russian the default language (forgive me for that please )
Disabled ADB secure.
Tweaks build.prop (to improve the quality of the photos).
Disabled block Assembly firmware, easily installed on the system, which has a size less than 2 GB (Yes, you can pick zip).
Bugs, jambs (it's not I made them):
Not working cyanogen setup wizard.
Crash software.
You can see the green demigod "AP Watchdog bark detected!" (crash software).
If you see a black demigod (this is the crash kernel), let me know.
Incorrectly read Bluetooth MAC address (Skite how to fix if anyone knows, my brain is not enough).
Source code: https://github.com/nitrogen-project
Attention! Immediately after installation to put Nitrogen Kernel!
Download: https://yadi.sk/d/GqqvKSddenX5R/Cyanogenmod/Cyanogenmod 12.1/Alpha
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Nice work @Mr.MEX, you've really got the point with this ROM.
akahroba said:
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Click to expand...
Click to collapse
Well or through twrp to delete CyanogenSetupWizard.apk
Loller79 said:
Nice work @Mr.MEX, you've really got the point with this ROM.
Click to expand...
Click to collapse
Thanks
P.S. Now compile the version from today, let's see, did they issue the green demigod's.
Well, fix WiFi (From mako N4) added.
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
If I disconnect the cellular network and WiFi lose imei ... how come?
I often appears green screen "AP watchdog detected shoulder." What causes this error?
guidoido004 said:
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
Click to expand...
Click to collapse
Yes, but this alpha no the second alpha will be delivered.
akahroba said:
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
Click to expand...
Click to collapse
The fix does not work on version 5.
zed923 said:
If I disconnect the cellular network and WiFi lose imei ... how come?
Click to expand...
Click to collapse
But from now on more.
st4ik said:
I often appears green screen "AP watchdog detected shoulder." What causes this error?
Click to expand...
Click to collapse
Curves hands of the guys from CM.
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
akahroba said:
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
Click to expand...
Click to collapse
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Mr.MEX said:
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Click to expand...
Click to collapse
Can you also send a pull request to cm team to add the camera libs?
Attached Wallpaper, initlogo, bootanimation - will be in the next version.
akahroba said:
Can you also send a pull request to cm team to add the camera libs?
Click to expand...
Click to collapse
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Mr.MEX said:
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Click to expand...
Click to collapse
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
akahroba said:
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
Click to expand...
Click to collapse
So he's euphoria compiles, CM hates...
dadi11 said:
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
Click to expand...
Click to collapse
Um for one thing, they don't add a vendor for the devices in the source - this may be the reason why they don't add fix for camera + need to make commits to the kernel (the driver from the runoff).
Related
Announcing PACE and PACE Plus for Find7.
PACE
This is pure AOSP plus with just enough CAF/CM enhancements to get it to run on a variety of hardware.
NOTE!!!
This is only for Find7a right now. I am working on adding support for Find7s. It should be ready in a few days.
Download:
pace44-find7-1.0.rc5.zip
md5=fa2984b63cdcbfab17b4118f397ddb66
Superuser (SuperSU):
superuser.zip
PACE Plus
This includes a few enhancements:
* Built-in SuperSU
* Gesture (swipey) keyboard
* Custom boot animation
* Density (DPI) changer
* Built-in adfree hosts
* Quick settings pulldown
* Torch
* Custom power menu
Planned enhancements:
* Theme support
* No-reboot installer
* ... Other suggestions?
Download:
paceplus44-find7-1.0.rc5.zip
md5=24d12e9aa482ea64d4ec0711af1e3c75
Known Issues:
* Location API (geolocation) used by apps like "Fences" does not work.
Changelog
v1.0rc5
* Initial build for Find7
Source:
github.com/pacerom
Hi, what is the differences between the branch v4.4 and v4.4plus with your source code on Github?
systop said:
Hi, what is the differences between the branch v4.4 and v4.4plus with your source code on Github?
Click to expand...
Click to collapse
The plus branch has the plus code with features listed in the OP.
tdm said:
The plus branch has the plus code with features listed in the OP.
Click to expand...
Click to collapse
I can get it, thank you for your so quick reply.
Then I wonder if I can roll back to 4.4.2? It is because I want to build a 4.4.2 pacerom using cm tree as a base rom to patch other roms like miui
Nice to see you here mate. Your rom on the OGP is excellent and I'm sure you will aim to please here as well
I did download and install an early *unannounced* build of this (before you had the thread up) and it was hard for me to pass the boot ani. I eventually booted in to safe mode and after that initial boot it worked great
*EDIT*
Flashed latest plus just now and it is flying. Would be awesome to have the device specific screen off gestures implemented. Only trouble so far is the AOSP keyboard force closes when swyping for me. Great work mate!
Hello, you can see some screenshots?
the rom is ready so how? does not need gapps? if so what is recommended MINI MODULAR PACKAGE ? thanks
Uanagana said:
Hello, you can see some screenshots?
the rom is ready so how? does not need gapps? if so what is recommended MINI MODULAR PACKAGE ? thanks
Click to expand...
Click to collapse
Im going to make this simple for you; ALWAYS flash gapps mini modular with every rom you ever use (unless you're flashing colorOS). I understand you are very new to XDA and perhaps a language barrier is the cause of some of the confusion (while corresponding with you in other threads)
@uppon2: The keyboard FC when using gestures should have been fixed. This is the fix commit:
https://github.com/pacerom/packages...mmit/9ddfe26215f035da036c620e69688c6721407811
That will depend on jni_unbundled_latinimegoogle existing, of course. It's provided in gapps.
If you have the "official" build with the md5 in the OP and you have gapps installed, I'll re-flash and re-test just to make sure something weird isn't going on.
I was on CM and Gummy for a couple months and I really got addicted to the tap2sleep/tap2wake stuff. I will definitely be trying to put those in soon. The other gesture stuff (circle for camera, vee for torch) may or may not make it in, depending on the amount of change required.
As for gapps, I have been using the CM recommended 20140606 package (linked here: http://wiki.cyanogenmod.org/w/Google_Apps) and it works well. Prior to last month I had been using the 20140105 package and it also worked well.
@Uanagana: Sorry no screen shots, just find a Nexus 5 screen shot and chop out the navbar.
tdm said:
@uppon2: The keyboard FC when using gestures should have been fixed. This is the fix commit:
https://github.com/pacerom/packages...mmit/9ddfe26215f035da036c620e69688c6721407811
That will depend on jni_unbundled_latinimegoogle existing, of course. It's provided in gapps.
If you have the "official" build with the md5 in the OP and you have gapps installed, I'll re-flash and re-test just to make sure something weird isn't going on.
I was on CM and Gummy for a couple months and I really got addicted to the tap2sleep/tap2wake stuff. I will definitely be trying to put those in soon. The other gesture stuff (circle for camera, vee for torch) may or may not make it in, depending on the amount of change required
Click to expand...
Click to collapse
I was reporting on the keyboard that is present in the rom. I had not flashed gapps at this stage so I'm assuming that will fix the problem.
I'm glad you're considering screen off gestures! Thank you
There are some duplicated ringtones in media and only difference is the letter case.
systop said:
There are some duplicated ringtones in media and only difference is the letter case.
Click to expand...
Click to collapse
I definitely see some weirdness with duplicated ring tones. Which ones do you see?
This may or may not be an aosp issue. I'll need to investigate.
tdm said:
I definitely see some weirdness with duplicated ring tones. Which ones do you see?
This may or may not be an aosp issue. I'll need to investigate.
Click to expand...
Click to collapse
Here is the list of duplicated ringtones:
arcturus.ogg vega.ogg Andromeda.ogg CanisMajor.ogg Perseus.ogg UrsaMinor.ogg hydra.ogg
Thanks for your rom, I have successfully patched a MIUI V5 4.4.4
Looks promising can't wait for find7 support thanks tdm
Here is my question, why do you remove the useful oppo custom setting from the CM tree?
systop said:
Here is my question, why do you remove the useful oppo custom setting from the CM tree?
Click to expand...
Click to collapse
I did not remove anything. I have my own tree and I am only adding things that are related to hardware support.
Which setting do you mean?
tdm said:
I did not remove anything. I have my own tree and I am only adding things that are related to hardware support.
Which setting do you mean?
Click to expand...
Click to collapse
You seems to remove the configpanel for common oppo phones which is included in cm tree
systop said:
You seems to remove the configpanel for common oppo phones which is included in cm tree
Click to expand...
Click to collapse
Ah yes the cmhw things. Is the anything in particular you want from that panel?
tdm said:
Ah yes the cmhw things. Is the anything in particular you want from that panel?
Click to expand...
Click to collapse
No, this config panel is not useful to me, and I only wonder if this panel is not compatible with the aosp?
systop said:
No, this config panel is not useful to me, and I only wonder if this panel is not compatible with the aosp?
Click to expand...
Click to collapse
I could add it if there is a need. But I have never wanted it myself.
Hi, I find that you add a kernel boot parameter: androidboot.selinux=permissive
I want to know why you add this? Is there any compatible issue with selinux between cm and pace?
Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Awesome!
kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
i do agree with jsevi83 pal even i tried with my noob knowledge now m bored
jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.
good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you
Any update ?
CyanogenMod 11 with crDroid additions for Xiaomi MiPad
!! IMPORTANT !!
xep.8800.org will be temporarely down from 29.03.15 for couple of weeks so it would be great if somebody do mirror of latest buld and post link here. Thx!
About:
Source built CM except proprietary blobs and binary kernel from stock MIUI rom.
This is not a port from another binary rom.
Click to expand...
Click to collapse
What's working:
It seems everything working for now..
Click to expand...
Click to collapse
Not working/Bugs:
"Wi-Fi region code" setting is broken. Do not touch it or it will break your wi-fi.
you tell me.. testing in progess..
Click to expand...
Click to collapse
Instructions:
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
Multirom Instructions:
1. Install TWRP Multirom Recovery
2. Reboot into TWRP and install multirom-20150205-v30-UNOFFICIAL-mocha.zip
3. Click "Advanced->Multirom" and flash your desired second rom.
4. Return to the installed roms listing, click fresh installed rom and click "Remove boot.img" (Due to closed kernel sources kexec-hardboot is not implemented so we need to remove boot.img)
5. Reboot. Select your desired rom from multirom menu
Click to expand...
Click to collapse
Downloads:
cm-11-20150327-UNOFFICIAL-mocha.zip
CWM
Multirom:
TWRP_multirom-v2.8.4-mocha.zip
multirom-20150205-v30-UNOFFICIAL-mocha.zip
I don't know if it is actually compiled with TEGRA optimizations but have created CWM flashable zip with stock bionic libraries. You can flash it on top of CM installation:
tegra_bionic.zip
Changelog:
15.02.15
* apply qcom bionic optimization
* build.prop dalvik etc tweaks
02.02.15
* Reboot to recovery fixed
* Recents view proportion fixed
26.01.15
* Synced with CM repo
* have enabled Display mirroring (miracast) though it does not work with my EZ dongle, sound is ok but screen is black. May be it'll work with another dongles...
21.01.15
* Update to the latest kernel from stock MIUI
20.01.15
* Sleep issue fixed
* Adopt nvcplsvc for CM & implement Performance Profile selection
18.01.15
* Synced up with CM repo.
* Added USB Mass Storage mode for external sd. Though it does not work along with ADB Debug enabled, need to be switched off when using UMS mode.
17.01.15
* Switch to CM's audio_effects and make Dirac plugin work. Equalizer crash fixed.
Click to expand...
Click to collapse
Links:
http://github.com/cyanogenmod
http://github.com/cristianomatos
https://github.com/faust93
Click to expand...
Click to collapse
I take no responsibility for what this may or may not do to your device.
Do not forget to click Donate button! It makes me work harder!
Thanks Pumbaster for your work!
My device doesn't seem to go to sleep...
WakeLockDetector shows Android System --> ConnectivityService as the main issue. BetterBatteryStats shows the same...
I tried turning location services off, froze Mobile Data and Mobile Network Configuration in Titanium Backup but that doesn't help. No checking if the same wakelock appears with wifi off...
Anyone with any clue? Or the same problem?
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Krystanos said:
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Click to expand...
Click to collapse
I used pico gapps myself and the june version is way smaller then the december version, then again I actually did try the december version as well and it seemed to work fine. So not sure, apart from the size...
About TWRP vs CWM, not sure. Guess it also should work with TWRP but haven't tried... CWM is needed for True Dual Boot, but that seems bugged anyway.
By me too. Battery drain is to much, device don't go to sleep...
zolikaDB said:
By me too. Battery drain is to much, device don't go to sleep...
Click to expand...
Click to collapse
Yeah, seems to be a common issue.
My device only goes to sleep when wifi is turned completely off. When I have it set to turn off when display is off I still get the wakelocks. I also have set the scanning for open wifi to off, location services turned off, etc.
For now I flashed back to the 0114 version as that one is working fine here...
If I can share some logs or anything, I'd be more then happy to!
@dagrim1: I hope, Pumbaster make new, fixed build
I Encounter Graphical Glitches with 3rd Party Browsers (Opera and UC Browser)
Chrome works fine so far. Also heavy Battery drain an 17/1
@faust93: what is with battery drain?
Did a very dirty try or replacing frameworks.jar but that didn't work...
Saw some wifiStateTracker errors and that and ConnectivityService seemed to be part of the framework, that's why I gave it a shot. 0118 still has the deespleep/wakelock issue btw...
I don't really care about dual boot. MIUI has so much limits. Once I go to CM, I don't think I'll be able to come back to MIUI...
But I'll stick to CWM, just in case...
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
dagrim1 said:
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
Click to expand...
Click to collapse
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
zolikaDB said:
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
Click to expand...
Click to collapse
I don't believe it's integrated in 0118, think that fixes some sd stuff...
I am currently running the 0118 build (with the wpa_supplicant.bin file replaced manually) and seems to be working pretty fine. Had some video issues with a certain app (video jumping a bit, stuttering) but think I fixed that with 'disable hardware overlay' in developer options.
Without the replaced .bin I also had a problem with turning off and on wifi. It would work when booting, but if I turned it off I couldn't turn it on again... The replaced .bin also fixes that. Now checking if antutu finishes it's run...
@dagrim1: hope, Pumbaster fix this problem!
Just another small question: full wipe will delete the /data partition too right ? So the ROM zip file will be deleted too ? Or am I missing something ?
Thanks.
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
jastonas said:
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
Click to expand...
Click to collapse
Unfortunately I tried to install CWM with fastboot and it failed to install... No specific error message.
I have seen a port of TWRP for MiPad. Have you tried this one, or the standard one?
How I wish I could just flash CM on my MiPad...
This is a port of Jolla's Sailfish OS for h815.
Standard disclaimer applies:
I take no responsibility if anything happens to your phone, if your alarm doesn't work or if it reboots when you call emergency numbers. Flash at your own risk.
Don't flash this if you need a fully working phone.
Beta? 1.1
What works:
Wifi, 4G/LTE, sound, calls, vibration, SMS, Jolla Store, GPS, accelerometer,
What doesn't:
Camera, bluetooth, stock browser (use web pirate), wifi passwords need to be entered after a reboot, some video playback crashes (can be fixed by using software decoding, for example gstreamer10-libav on openrepos)
Possibly more, please report any issues
Install instructions:
Make sure you have a backup of anything you don't want to lose, preferably not on the device
Full wipe (might work without)
Flash LineageOS 14.1
Flash sailfishos-h815
Ignore any "no system installed" warnings from TWRP
Please note that this is not an Android ROM. Your Android apps will not work until someone gets sfdroid working.
Thanks to:
The friendly guys at #sailfishos-porters for helping me out a lot
Jolla for developing Sailfish OS
Download links: a few posts below
XDA:DevDB Information
[H815] Sailfish OS port, ROM for the LG G4
Contributors
kamnxt
ROM OS Version: 7.x Nougat
Based On: Sailfish OS
Version Information
Status: Beta
Current Beta Version: 11.02.18
Beta Release Date: 2018-02-11
Created 2017-07-29
Last Updated 2018-02-12
Downloads:
LineageOS 14.1:
I'm using the version from here right now:
https://www.lineageoslog.com/14.1/h815#201711070000
Sailfish OS: Latest here: https://androidfilehost.com/?w=files&flid=202570
All versions here: https://androidfilehost.com/?w=files&flid=202568
My sources:
https://github.com/kamnxt/droid-hal-h815
https://github.com/kamnxt/hybris-boot
https://github.com/kamnxt/android_kernel_lge_msm8992
Will try to upload everything soon
Changelog:
alpha 1 - 29.07.2017:
Initial release
Would be nice for someone to test. Also, formatting needs sorted for this first post along with source code links etc
OP, just make few 'reserved' posts, you need to have 10 posts to post a link
Sent from my LG-H815 using Tapatalk
Kye2000 said:
Would be nice for someone to test. Also, formatting needs sorted for this first post along with source code links etc
Click to expand...
Click to collapse
Minto107 said:
OP, just make few 'reserved' posts, you need to have 10 posts to post a link
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Done, will post links now
kamnxt said:
Done, will post links now
Click to expand...
Click to collapse
i flashed now but i am stuck here
gentr said:
i flashed now but i am stuck here
Click to expand...
Click to collapse
That's a part of the tutorial. If it doesn't work properly, you can try to skip it by tapping the corners of the screen from top left clockwise.
kamnxt said:
That's a part of the tutorial. If it doesn't work properly, you can try to skip it by tapping the corners of the screen from top left clockwise.
Click to expand...
Click to collapse
It's easy os system and very attractive to use them, hope for the new update very soon.
Great news!
When camera and browser will start working I'll try the port, till then... it's too much alpha for me
Thanks for the port!
Laghie said:
Great news!
When camera and browser will start working I'll try the port, till then... it's too much alpha for me
Thanks for the port!
Click to expand...
Click to collapse
You can use an unofficial browser like Webcat instead. Camera doesn't work yet though. I'll try to release a version with qtscenegraph-adaptation fixed soon (fixes black images).
Hello! Are you still working on this?
Laghie said:
Hello! Are you still working on this?
Click to expand...
Click to collapse
Hey! I've been kind of busy lately, but I was thinking about updating it recently. I can try to compile a new version if you want (hopefully including a fix for the pink screen issue).
That would be nice. Also a little status update is Glas
Thanks! But take your time, life's more important that alpha testing
BTW, is it possible to dual boot android and sailfish?
Laghie said:
Thanks! But take your time, life's more important that alpha testing
BTW, is it possible to dual boot android and sailfish?
Click to expand...
Click to collapse
You can dualboot by modifying fstab in the kernel and recovery to point the /data and /system to sdcard.
But you need quick sdcard to not be totally unusable.
Status update time!
I'm setting up the build environment on my new laptop (it's been a while since I last messed around with SFOS...) New version should be coming soon™ (hopefully within a few days). Trying to build with a newer version of LineageOS as well, so we'll see if that works.
Yes please. Would love to see this working. There isn't enough new stuff out there for the G4 and this would be awesome.
#ApolloLiteProblems said:
Yes please. Would love to see this working. There isn't enough new stuff out there for the G4 and this would be awesome.
Click to expand...
Click to collapse
Seems like I lost some of the files from the last time I got things working... I need to find out how I got sound working, since now it no longer works... I'll see if I can get it working again.
Awesome.
LINEAGE OS
This is an Alpha build of lineageos15.1
Working:
-RIL
-Bluetooth
-Camera (at least 1 of them)
Not Working:
-Probably selinux (did not try enforcing kernel yet)
-Probably encryption (logcat says it works...)
-Wlan (maybe bcs some files from vendor/vendor_system in /system are missing)
-2nd camera (fix could be to use micamera app)
-Probably more
Instructions:
-Download V9.6.11.0.ODLMIFF_8.1 original rom
-go to V9.6.11.0.ODLMIFF/images
-Replace boot.img, with boot.img
-Replace system.img and system_other.img with system.img
-use the flash_all script. THIS WILL WIPE ALL YOUR DATA, EVERYTHING! if you want to go back now (or later) just put the original images back again and use flash_all_except_storage
-Directly after the device reboots by itself, press vol up + power (u might have to hold it until device reboots again) to enter los recovery
-"factory reset--> wipe data"
-If you want TWRP "advanced-->reboot bootloader" and flash TWRP accordingly to thread, then u can flash gapps/mods.
-reboot
-give it time to boot
Source:
ROM
Device branch "los15"
msm8953-device
Kernel
To finish, I WON'T CONTINUE THIS ROM the trees are working, P vendor is there, an adaption to los16 should be possible based on that. Also, i prefer OMNIROM (which i will try to build next).
Thanks goes to:
-Google for the search engine as well as for the source code
-Cozzmi13 for taking some time to show me the basics.
-Lineageos
-Github
-ada12 for offering his help
thankssss
im wait until wlan fix, but thanks for your effort
CreateYourDream said:
im wait until wlan fix, but thanks for your effort
Click to expand...
Click to collapse
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
It would be nice to have logs, then I could help.
If you ever need help with your omnirom build i would love to help out with everything that i can. Daisy really needs more support to be a very good device.
hi!
anyone know, is this build of LOS 15.1 support correct notch area?
and what about Onmi build?
i want give possible help if need)
Thanks for your work, I hope soon More roms for this great device
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
wertus33333 said:
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
Click to expand...
Click to collapse
not worked
and usb-tethering too
eremitein said:
sometimes after tapping screen blink with red border
Click to expand...
Click to collapse
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Can anyone give me the logs for the bugs?
Is this Rom abandoned?
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
Yup. This phone is abandoned in general, which is a shame
eremitein said:
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
Click to expand...
Click to collapse
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Nice to know: The blinking red borders show layout updates, they flash in all eng (=developer) builds. If changing the build variant to userdebug (debuging enabled) or user (oem/production builds with few debuging enabled) they vanish.
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
kftX said:
Yup. This phone is abandoned in general, which is a shame
Click to expand...
Click to collapse
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience. Also, all of us do this in our spare time and therefore it can take time. If you want to speed up the build, supply logs (clean install rom, install adb on pc, execute
Code:
adb bugreport > bugreportDATE.txt
or
Code:
adb logcat > logcatDATE.txt
, share the reports), error descriptions (like @eremitein) and/or read on how to build a rom for a device yourself.
eremitein said:
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Click to expand...
Click to collapse
oh, you already saw this xD
wertus33333 said:
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience.
Click to expand...
Click to collapse
Editing this out of respect even though none was shown.
Also, I would love to help but with the lack of a proper working TWRP (encryption, restore backup issues) I really can't give it the time needed with all the stuff I'd have to reinstall every time, since I need my phone up and working nearly 100% of the time. If a decent version TWRP is released, I'll gladly help.
Glad you're still working on this though, just don't act like we should've known that you still where when the thread was dead for months. Good luck.
wertus33333 said:
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Click to expand...
Click to collapse
successful build, always happy to help
is there any reason you build los 15.1 instead of 16?
skyline91 said:
is there any reason you build los 15.1 instead of 16?
Click to expand...
Click to collapse
At the time i built the rom only 8.1 vendor (8.1 official rom) was avaiable. as i'm not really experienced with android it was easier to build 8.1 rom instead of trying to port vendor to 9.0 (while 9.0 vendor would have defenitely be officially out in a month or 2 ) and build los16. porting the device tree from 15.1 to 16.0 should be easy. Also, i don't like los, i want omni .