[Lollipop] 1033xt GPE Converted devices Discusssions - Moto G General

Edit : All issue is solved now check this post
Hi
This post is only intended for GPE converted 1033 users. i've seen many guys complaining in Dev section.
im a GPE converted 1033 user since the day i unlocked the bootloader.
in recent past had a issue with all the CM12 based roms like
1. Encryption Error due to EXT4 partition
2. WiFi wont work (CM integrated wifi modules into kernel)
3. Roms recognize my device as Dual SIM after converting to GPE
4. Continuous System UI force closes
earlier, all this problem solved by flashing Donkey Kang Kernel. Recently dev of DKK stopped support for our device
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
summary
RAMDISK form DKK3.8
Zimage from CM12 based Kernel(Integrated WiFi Modules)
How to install.
the provided file is boot.img directly (not a flashable zip. )
Latest TWRP supports flashing img files directly. please make use of it else you can also use apps like rashr which is available in playstore.
please make sure you know what you are doing before messing with your device.
PS : i'm not a developer
Edit : i tested with Resurrection Rom and i can confirm everything works as a single sim device on GPE converted 1033
Edit1 : tested with validus build 17-01 works prefectly
Edit2 : all credits to the developers

tell me the changes needed i'll rebuild my base around it..

bharat_goku said:
tell me the changes needed i'll rebuild my base around it..
Click to expand...
Click to collapse
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source

reversegear said:
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source
Click to expand...
Click to collapse
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app

Differences between stock kernel and modified kernels
Stock kernel device recognised as dual sim in terminal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Modified kernel device recognised as gpe in terminal

Flashhhh said:
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Does this work for u

reversegear said:
Does this work for u
Click to expand...
Click to collapse
I haven't tested yet but it should work
Sent from my Moto G using XDA Free mobile app

can i flash this boot.img on donkey kang kernel or should reflash rom and then flash boot.img?
edit:just flashed it using rashr app on candy rom above donkey kernel and everything is fine...thanks for this fix

Will try now..

worked for me
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.

prasoon27 said:
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.
Click to expand...
Click to collapse
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589

reversegear said:
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589
Click to expand...
Click to collapse
Thanks for the response. You are right, there are no multitasking issues.

Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..

padhu1989 said:
Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..
Click to expand...
Click to collapse
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.

reversegear said:
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.
Click to expand...
Click to collapse
i think it happen to people who updated to stock lollipop or something like that...i never enconter it too bcz i never gone back to stock

I found the cause of this "bug" gpe converted. In cm11 when has the file persist.radio.multisim.config empty into /data/property is recognized as single sim (the file is created automacally on reboot, even if manually delete). Donkey lp too don't create this file automatically in cm12 (what hack he used i don't know), but if create manually or made a dirty flash from cm11 all kernels recognized as single sim (due file created on cm11), if delete or made a factory reset cm12 back to be recognized as dual.
I hope that info help devs to fix in official roms :fingers-crossed:

Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing

reversegear said:
Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing
Click to expand...
Click to collapse
Yeah it not working on rr it getting stuck on initializing

reversegear said:
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
Click to expand...
Click to collapse
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.

ren2r said:
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.
Click to expand...
Click to collapse
Glad to here that..
You can share ur boot.img here with the permission of the actual kernel/rom developers. by giving them credits
Does compass tile work in ur modified kernel
Edit:
I never knew still so many GPE converted 1033 users on XDA :happy:

Related

[Q] Stock 4.4 patched kernel for multirom

Can anyone help me finding stock Kernel w/ kexec-hardboot patch for Android 4.4 for multirom?
Im not able to get the version of my primary ROM is based on
(or)
Can i use third-party kernel?
...
Im on 4.4 (KRT16O) Manually flashed factory image (developers.google. com/android/nexus/images#occamkrt16o).
Unfortunately i tried installing other kernel and encountered boot-loop and I had to flash factory image again..
(I used multirom before [before flashing stock 4.4] and used stock 4.3 JWRXXX kexec-hardboot patch kernel. That worked fine.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
eksasol said:
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
Click to expand...
Click to collapse
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Sidnexus4 said:
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Click to expand...
Click to collapse
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasnt been releaded yet.
simms22 said:
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasn't been releaded yet.
Click to expand...
Click to collapse
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Sidnexus4 said:
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Click to expand...
Click to collapse
you can try trinity kernel as well, it has the multirom stuff included, and runs on 4.4 roms. heres the latest trinity, tf18b http://goo.gl/RvKALI
Lianro kernel Neo17 worked great for multirom on NEXUS 5 PORT 4.4 KRT16O : http://forum.xda-developers.com/showthread.php?t=2507021 (Rom is far better than the original stock image. It includes all the missing features on stock)
Thanks everyone for the support :victory:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
eksasol said:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
Click to expand...
Click to collapse
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Sidnexus4 said:
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Click to expand...
Click to collapse
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
JJMACCA said:
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
Click to expand...
Click to collapse
I think its needed for android roms too. when ever i need to boot into another rom after flashing it says knex hardboot needed and it doesn't start up..
As i posted earlier neo kernel worked fine on 4.4(internal rom) with dePRIMAtor file (www.androidfilehost. com/?a=show&w=files&flid=9271).
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
mar_sch said:
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
Click to expand...
Click to collapse
Great!
Can you give us the link here??
activexda said:
Great!
Can you give us the link here??
Click to expand...
Click to collapse
here z the page... check for the link in second post..
http://forum.xda-developers.com/showthread.php?t=2472295

[ROM][4.4.2][jubei][Beanstalk and Fenris]

Fenris https://en.wikipedia.org/wiki/Fenrir is one evil wolf.
ooops a little to evil i think, withdrawn until i review the buzz
Not a Moderator to Tell what to do but i think this is not correct place to start ROM thread
http://forum.xda-developers.com/nexus-7-2013/development
or
http://forum.xda-developers.com/nexus-7-2013/orig-development
i maybe completely wrong too
vinumsv said:
Not a Moderator to Tell what to do but i think this is not correct place to start ROM thread
http://forum.xda-developers.com/nexus-7-2013/development
or
http://forum.xda-developers.com/nexus-7-2013/orig-development
i maybe completely wrong too
Click to expand...
Click to collapse
yep thats what i thought to, then read this at the top of the dev forum
http://forum.xda-developers.com/showthread.php?t=2380904
which basically said if not you own it do not post it there, also suggested posting it here.
Since i only really tweaked the zip of beanstalk to produce Fenris, and just added a little bash code, dont know if it counts as my work, i did not compile anything at all.
Having said that am back at my linux box in 2 days and will compile it from scratch then
Fenris V6 up
First of all, thank you for your effort around making tweaking and modding BeanStalk rom.
After, regarding where it should go, I think it "Android Development" category would fit, but I'm sure someone will confirm and move there if necessary.
Sounds great, can't wait to get home and try it out. I'm currently using PAC, but it lacks a lot of the usual PAC features. Same is for paranoid for Flo, it's almost completely pure AOSP and lacks a lot of the usual features.
Sent from my Nexus 7 using XDA Premium 4 mobile app
What kernel should I use for this - CAF or AOSP?
Sent from my Nexus 7 using XDA Premium 4 mobile app
jubei_mitsuyoshi said:
Fenris V6 up
Click to expand...
Click to collapse
I'll be happy if it just doesn't random reboot like the CM11 does. So far, only stock is solid.
jmdearras said:
I'll be happy if it just doesn't random reboot like the CM11 does. So far, only stock is solid.
Click to expand...
Click to collapse
Nope zero problems for me
V6 semed to have got lost in the air somewhere , but v7 ( pretty stable i think just doing last of the tests ) is up and very very very good
A bit of a warning here, Fenris is not like other roms, to get the best out of it either read the setup instructions with a fine tooth comb, or be VERY familiar with lucky patcher already
Fenris V8 ( what i hope is the last version ) is up, so far no big bugs
jubei_mitsuyoshi said:
Fenris V8 ( what i hope is the last version ) is up, so far no big bugs
Click to expand...
Click to collapse
V8 fails to flash. Twrp gave me a failed updater binary error (or something like that) error.
Sent from my Nexus 7 (2013)
oadam11 said:
V8 fails to flash. Twrp gave me a failed updater binary error (or something like that) error.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Ok am on it, will have a look and fix if necessary within the hour,
There is a separate problem, the new build of beanstalk i am using seems to have broken bluetooth, i have just checked on a clean unmodified beanstalk / fresh flash and def something up with the Bluetooth, since im not compiling it yet doubt can fix, am revering back to the previous release and checking its working on that, if not going on that will be changing rom base.
Just flashed my local V8 with no problems, twice to check,
So has to be a upload/download issue, can you try re-downloading and try again ?, if still issue will re-upload file.
What does the TWRP window say ? does it fail at a script line or fail at the beginning ?
jubei_mitsuyoshi said:
Just flashed my local V8 with no problems, twice to check,
So has to be a upload/download issue, can you try re-downloading and try again ?, if still issue will re-upload file.
What does the TWRP window say ? does it fail at a script line or fail at the beginning ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I redownloaded and tried it again. The attached picture shows the error I am getting. I am using multirom if that makes a difference
Sent from my LG-VS980
oadam11 said:
View attachment 2641154
I redownloaded and tried it again. The attached picture shows the error I am getting. I am using multirom if that makes a difference
Sent from my LG-VS980
Click to expand...
Click to collapse
hmm yes obviously an issue when flashing as secondary rom, maybe something to do with the new " check journals gone with a script " feature, will remove it and see if that makes a difference, will call it v8.1 and do it for tonight.
Ps seems Bluetooth does work, just the options>blutooth>on/of switch is flaky, can be swiched well with the drop-down panels.
Its a small bug and do not think its reason to switch base rom.
Have checked pairing with few devices,all pair, by no means a good spread
8.1 is uploaded , can i ask what TWRP you are using ? , i dont recognise your screenshots, is it the multirom app ? I use 2.7 multirom TWRP and it does not look like that ( in fact your screens look much better )
jubei_mitsuyoshi said:
8.1 is uploaded , can i ask what TWRP you are using ? , i dont recognise your screenshots, is it the multirom app ? I use 2.7 multirom TWRP and it does not look like that ( in fact your screens look much better )
Click to expand...
Click to collapse
I'm on the latest multirom 2.7. I use a twrp theme so that's why it looks different. Thanks. I'm going to try 8.1 once its done downloading
Here is the forum to the theme that I use
http://forum.xda-developers.com/showthread.php?t=2409432
[THEME][N7.2] TWRP Holofied - Black / Dark / Light / Play / XDA / MultiROM [12/03/14]
Sent from my Nexus 7
oadam11 said:
I'm on the latest multirom 2.7. I use a twrp theme so that's why it looks different. Thanks. I'm going to try 8.1 once its done downloading
Here is the forum to the theme that I use
http://forum.xda-developers.com/showthread.php?t=2409432
[THEME][N7.2] TWRP Holofied - Black / Dark / Light / Play / XDA / MultiROM [12/03/14]
Sent from my Nexus 7
Click to expand...
Click to collapse
Ahhh thank you very very much, must say one learns something new every day on XDA
Ok found/fixed the issue with Fenris and multirom, the multirom environment is incompatible with my ext4 journal fix, hence i have made a version without my ext4 fix, its in the same folder but with a "multirom" tag, just tested and will be good.
I do a fair amount of weird kernel tweaking in the init.d , no idea if any of that is multirom complaint, certainly have not tested it in that env
V9 is up, this is final stable version, which i use every day, lead post updated.

[Ze Master Patch][I9505 KK Roms to I9295 KK Roms(cm based only)][No More Jelly !]

Have you been looking at the I9505 Forums for a rom and you felt JELLY ?? ... Don't worry the days of being JELLY are seeing the light of the end .​
OKK Lets get started .​
What's this ?
Ze Master Patch is as you see in the name is a patch but not any patch , it's a magical recovery flash-able zip that makes any cm based rom for the I9505 installable on our phone with some slight modifications which will be covered in the guide later , what this pacakge does is replace or I9505 stuff with our I9295 stuff all libs all binaries and even a boot image etc ... let's continue further .
Click to expand...
Click to collapse
Why is this useful ?
IDK ... maybe to allow you to watch p*rn on more roms
Click to expand...
Click to collapse
Wow !! ... How Did You Do This ??
A good magician never tells his secrets to anybody ... -naaah just kidding- ... it all started when i was bored and wanted to do something so i thought of something special i took the branches of a dev here in this community (will tell you more about him later) and noted the names of the proprietary files and extracted them 1 by 1 and flashed them upon a I9505 rom with a kernel made by the same dev i am going to tell you about annnnnnnnnnnnnnnnd voilla i got some roms booting wooopa gammmnam style party in the chair !!.
Click to expand...
Click to collapse
What Shall i need to know more ?
You need a lot more !! you need to know 3 more things
1. The roms you can choose
A.You have to choose a rom that is based on cm
B. A Jflte (universal build) or Jfltexx (Regular I9295 Build) eg :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C. You have to do some modifications to the zip file before flashing
Extract your zip anywhere on the pc
Once extracted open META-INF/com/google/android/updater-script with notepad++
Delete the prop lines (if they exist) eg :
Repackge rom and flash it or read instructions or make collect dust for moments
Click to expand...
Click to collapse
Click to expand...
Click to collapse
General Installation notes
1. Download the rom you want
2. Do the nesscary modifications if they exist
3. Place the rom on your sdcard
4. Make a backup
5. Wipe everything from system to data to dalvik to normal cache
6. Flash you rom
7. Flash the patch
8. Come here give me thumbs up and go away and enjoy !!
Click to expand...
Click to collapse
Bugs
High
none
Medium
Not all roms are compaitible ... a rom with a proprietary framework naming won't work like pac man rom that needs some more work
Click to expand...
Click to collapse
Low
Device name appears as I9505 ... if you want to change that make a simple build.prop edit :good::good:
Click to expand...
Click to collapse
creits and other things in next posts
Downloads
v1 5/13/2014 5:49pm get it here
v2 5/14/2014 8:01pm get it here
for credits
Gave it a short try with official cm11 for s4.
No wifi
No Bluetooth
Hardware Menu and back Keys not working.
Will give it another try this weekend, when I have more time for testing this.
Gesendet von meinem GT-I9295 mit Tapatalk
4cr0ph3t said:
Gave it a short try with official cm11 for s4.
No wifi
No Bluetooth
Hardware Menu and back Keys not working.
Will give it another try this weekend, when I have more time for testing this.
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Thanks ... Looking forward for your report ... I think I have fix for hardware keys ... The other two need some work , will upload another version when I get from school .
common people ... it's v2 cant no one test ?
Sorry, i just changed to a SOKP ROM for the time being. When changing back tot CM i will give it a try. Thanks for your efforts cause it would open a lot of opportunities I guess.
Sent from my GT-I9295 using Tapatalk
mythi said:
common people ... it's v2 cant no one test ?
Click to expand...
Click to collapse
Will test this weekend.
To busy right now.
Gesendet von meinem GT-I9295 mit Tapatalk
mythi said:
common people ... it's v2 cant no one test ?
Click to expand...
Click to collapse
installed it with CM11 for S4
- Wifi still not working
- Bluetooth not working (S4 Bluetooth works with active therefore no need to flash any Bluetooth files)
Could not test Camera though as was busy, will check and revert later
Edit: Camera App not showing up, installed google camera which also did not show up. seems to be an issue with the firmware / libs
GPS Working, but compass is not showing direction, checked with GPS Status
Edit2: Bluetooth including messaging (Bluetooth map service) works perfectly with original CM11 for S4 files (deleted the /app and /etc/Bluetooth folders from the ze_masterpatch)
JASONRR said:
installed it with CM11 for S4
- Wifi still not working
- Bluetooth not working (S4 Bluetooth works with active therefore no need to flash any Bluetooth files)
Could not test Camera though as was busy, will check and revert later
Edit: Camera App not showing up, installed google camera which also did not show up. seems to be an issue with the firmware / libs
GPS Working, but compass is not showing direction, checked with GPS Status
Edit2: Bluetooth including messaging (Bluetooth map service) works perfectly with original CM11 for S4 files (deleted the /app and /etc/Bluetooth folders from the ze_masterpatch)
Click to expand...
Click to collapse
ok thanks ... v3 will be up soon :fingers-crossed:
is v3 up?
no longer needed to use this , i have started many ports from source which is better
mythi said:
no longer needed to use this , i have started many ports from source which is better
Click to expand...
Click to collapse
So maybe this should be unpinned?
I've found for the 9295 with kitkat this two images/threads:
http://forum.xda-developers.com/showthread.php?t=2760693
http://forum.xda-developers.com/galaxy-s4-active/development/rom-pac-version-t2821017
But both have some "tweaks" and such, i like more xposed modifying. Can you build a AOSP rom, just with all hardware features working?
Btw, the S4active should really have a own subforum...
defim said:
So maybe this should be unpinned?
...
Can you build a AOSP rom, just with all hardware features working?
Btw, the S4active should really have a own subforum...
Click to expand...
Click to collapse
AOSP is work in progress here
http://forum.xda-developers.com/showthread.php?p=54174595
In case you didn't notice - you have just posted in the very own forum for S4 Active :screwy: The link to AOSP is also inside this forum:
The Original Development branch where porting threads of virtually identical devices (S4 - S4 Active) can get awarded with warnings and moderator examination...
Rules http://forum.xda-developers.com/showthread.php?p=44648356
O-T said:
AOSP is work in progress here
http://forum.xda-developers.com/showthread.php?p=54174595
In case you didn't notice - you have just posted in the very own forum for S4 Active :screwy: The link to AOSP is also inside this forum:
The Original Development branch where porting threads of virtually identical devices (S4 - S4 Active) can get awarded with warnings and moderator examination...
Rules http://forum.xda-developers.com/showthread.php?p=44648356
Click to expand...
Click to collapse
Many thanks! Seems is was really confused... I hadnt found the linked thread
Dear Mythi, can I use this tool for porting cm based miui for 9505 to our device?
Sent from my GT-I9295 using XDA Premium 4 mobile app
6783 said:
Dear Mythi, can I use this tool for porting cm based miui for 9505 to our device?
Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NO , it won't work as the blobs inside this are deprecated please use other roms as base such as cm
Request
Please Mythi, you can port Flyme OS 4.1.2 ( 4.4.4 ) already ported in GT i9505
can you port miui rom from s4 to our devices? please
note 5 or s7 rom for s4 i9295
please somebody make a special rom i9295 owners, thanks for reading

Discussion | OmniROM 4.4.4 | Motorola Moto E

OmniROM 4.4.4 Discussion and Support Thread
I have built the OmniROM 4.4.4 for our beloved device!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still its under testing! I need some patches from other developers to make this more stable and usable!
And this thread is more about information and announcements for this rom.
Please don't ask for ETAs because I don't have a build server and the build compiled with GCC 4.8.2 and O2 optimisation (iykwim), it took 7-8 hours for single build.
Which sources u are using???
Sent from my XT1022 using xda premium
Regarding Sources
nisu4717 said:
Which sources u are using???
Sent from my XT1022 using xda premium
Click to expand...
Click to collapse
Well, I first based my trees with Percy's CM11 sources.
Later I modified many of the files that were causing trouble while building and also changed the files as per omni dependencies.
The new source will be cleaned and uploaded once I test the rom and release it
I just uploaded the support trees on my Git: https://github.com/ramsudharsan/android_device_moto
https://github.com/ramsudharsan/device_qcom
Is the wifi bug solved, since cm by percy the wifi bug is present
amarjit_rsingh said:
Is the wifi bug solved, since cm by percy the wifi bug is present
Click to expand...
Click to collapse
Bro I have uploaded my build! I need someone to test and report me! I am not usually good with kernels. Hence I doubt whether my build will boot up or not. I faced a error when compiling WiFi and I solved it by some modification. Hence, it will be better if someone test it.
Let me link the first build here:
http://www.mediafire.com/download/6zr7p58st68cd5h/omni-4.4.4-20140914-condor-NIGHTLY.zip
Hope I get some positive feedback.
Sent from my XT1022 using XDA Free mobile app
#buzz said:
Bro I have uploaded my build! I need someone to test and report me! I am not usually good with kernels. Hence I doubt whether my build will boot up or not. I faced a error when compiling WiFi and I solved it by some modification. Hence, it will be better if someone test it.
Let me link the first build here:
http://www.mediafire.com/download/6zr7p58st68cd5h/omni-4.4.4-20140914-condor-NIGHTLY.zip
Hope I get some positive feedback.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
downloading and testing , will give the reviews approximately by tomorrow or the day after
HELLO
Your rom doesnot boot, you need to update your sources, device tree and kernel sources
xperiafan13 said:
Your rom doesnot boot, you need to update your sources, device tree and kernel sources
Click to expand...
Click to collapse
Yeah , btw , try installing the launcher from the zip file ... read what you get there..
Review
xperiafan13 said:
Your rom doesnot boot, you need to update your sources, device tree and kernel sources
Click to expand...
Click to collapse
Bro I agree that my rom didn't boot but I heard from priyank.g that he used multirom to flash. Also he reported that the screen is keeping on flashing. Will use of TWRP solve the issue?
And bro, is adb working at the boot?
The device tree is perfect afaik, coz it won't build properly if it doesn't.
It might be the kernel issues. Will resolve it and make one more nightly build by today or tomorrow!
OmniROM 4.4.4: Moto E: Nightly Build 2
Guys, I just made another nightly build!
I am very sorry for my previous build and sorry for you guys that I wasted 190MB of your bandwidth!
I have modified the kernel source for this build!
Again I hope it boot!
Here's the download: http://www.mediafire.com/download/83d9bn1b34uo3cx/omni-4.4.4-20140915-condor-NIGHTLY.zip
Did Anyone Tried It?????????:thumbup:
Sent from my GT-I9300 using XDA Free mobile app
I'm having a bootloop!!!
BDW will you be able to build Paranoid Android 4.6? taking percy_g2's sources?
I'm currently on his rom now, cm11 (nightly 7)
i help
Hey man , I help you to Test builds in omni rom OK , Send new builds and i test
#buzz said:
Guys, I just made another nightly build!
I am very sorry for my previous build and sorry for you guys that I wasted 190MB of your bandwidth!
I have modified the kernel source for this build!
Again I hope it boot!
Here's the download: http://www.mediafire.com/download/83d9bn1b34uo3cx/omni-4.4.4-20140915-condor-NIGHTLY.zip
Click to expand...
Click to collapse
Well.. I tried twrp but installed it on top of CM11 (percy#7) and also tried multiROM .. Same result.. I will try injecting a new boot sector from cm 11 wait till I give another review please
EDIT: Still not booting .. Sorry
Downloading it [emoji106]
Don't just say thanks press the button
Not booting bro .... [emoji17]
Don't just say thanks press the button
OmniROM 4.4.4: Moto E: Nightly Build 3
As xperiafan13 suggested, I worked on the device tree though I am not sure about the kernel. I made a new build little while ago on 23/09/2014 and I was sending PM to some trusted person I could find. But none of them were able to test it. And I know blind builds are not allowed on xda. Hence, I was studying what made the CyanogenMod and its derivative roms boot up while Omni don't! So I applied some patches, made by myself and made this new build. If it works,we can integrate the patches to any other open source rom to make it boot but only if this build work.
Public Link: http://www.mediafire.com/download/g63ha9qelq4ccxs/omni-4.4.4-20140923-condor-NIGHTLY.zip
P.S I am trying my best to give the best to the people. Please if possible, give me logs if you face any problem.
I will try it downloading[emoji106]
Edit: still not booting up
I hope it works now :thumbup:
Sent from my XT1022 using XDA Free mobile app
Are there any particular specs you need?
#buzz said:
Please don't ask for ETAs because I don't have a build server and the build compiled with GCC 4.8.2 and O2 optimisation (iykwim), it took 7-8 hours for single build.
Click to expand...
Click to collapse

OMNI 6.0.1 vanilla build

Hi guys,
I built the latest omnirom for our Z3 compact using sources kindly provided and created by Humberto Borba. There will be very little support for this ROM but I wanted to provide it as is for anyone who wants to use a custom ROM as the current choices for our device are pretty limited. I am not a DEV for this device but I do know how to build.
You will need an UNLOCKED BOOTLOADER
So all that goes with that ie loss of DRM etc applies here. You will also need the latest version of the bootloader to get this to work, so ensure you are coming from an uptodate 5.1.1 ROM or any 6.0.1 ROM
If you want to install GAPPS then you will need to do it immediately after installing the ROM. Do not reboot and then install GAPPs
Whats more the camera does have the fisheye lens distortion. Anyone following the AOSP dev work will be familiar with all the issues on the phone.
Again I am not posting this as a DEV project or in the DEV channels as I didn't develop it and won't be supporting it in any meaningful way.
kind regards
Download
Updated link to folder of all builds so I won't need to update links anymore
Can you take screenshort
Ill take some screen shots on the next build. Omni have just added a new camera for snap dragon devices so I am keen to give that a spin
Wifi problem report
Thx for work.
Flashed firmware, i meet wifi problem.
Turned on, but not listed any APs.
2.4 and 5 Ghz both.
Is there anyone who get same problem?
Or any information for Fix?
Screen shots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Camera shots
BaekHo said:
Thx for work.
Flashed firmware, i meet wifi problem.
Turned on, but not listed any APs.
2.4 and 5 Ghz both.
Is there anyone who get same problem?
Or any information for Fix?
Click to expand...
Click to collapse
I don't have that issue as you can see from above. Did you perform a clean flash?
mcgi5sr2 said:
I don't have that issue as you can see from above. Did you perform a clean flash?
Click to expand...
Click to collapse
Yeah, unfortunately i wifed System, cache, data, dalvic...
But you don't had any problem.
I guess i had mistake or does not it correctly...
I'll try again! Thanks for your attention!
Hi! Thanks for your work with thiese vanilla build. I'm so impressed the whole flash procedure. I'm came from slimm1.5 rom, wiped data, cache, dalvik, system in twrp 3.0.2.0 then flashed omnirom homemade, after that slimm gapps. The whole flash time, the first time boot was incredible fast. The whole system was quickiest to the nowdays roms. I tested the new camera, but i think the fiah eye bug is still there.. But maybe not so "big eye" like previously aosp roms. Anyway, I like it. Now, testing the battery life
Sent from my D5803 using XDA-Developers mobile app
BaekHo said:
Yeah, unfortunately i wifed System, cache, data, dalvic...
But you don't had any problem.
I guess i had mistake or does not it correctly...
I'll try again! Thanks for your attention!
Click to expand...
Click to collapse
Oops... I got same problem.
Does Clean flashing, Wipe and boot normal.
But I couldn't catch WiFi signal.
I'm using D5833 @korea.
Before find way for fix, stay on 5.1.1 stock...
BaekHo said:
Oops... I got same problem.
Does Clean flashing, Wipe and boot normal.
But I couldn't catch WiFi signal.
I'm using D5833 @korea.
Before find way for fix, stay on 5.1.1 stock...
Click to expand...
Click to collapse
Sorry to hear this. Are the wifi bands any different in Korea?
[/COLOR]
mcgi5sr2 said:
Sorry to hear this. Are the wifi bands any different in Korea?
Click to expand...
Click to collapse
I guess there is no critical difference with Most other countrie's 2.4 and 5.0 GHz 802.11 channels.
Found channels on my wireless router, same with bellow's information about In Korea sections.
https://en.m.wikipedia.org/wiki/List_of_WLAN_channels
@mcgi5sr2 thank's 4 building a custom rom and being motivated to contribute here. do you see any way to get rid of the fisheye camera bug? i've bought my z3c in january 2015 already and built/offered a custom rom (pacman) some weeks later. i stopped contributions 3 months later, when i went to holidays and needed a fully working camera. since then i saw MANY MANY talented and motivated developers & contributers here coming and leaving within only 1 year. i'm personally using concept rom which i find quite satisfying for every day use.
but i think there won't be any wide rom developement for that nice little device if the pictures taken keep being that unusable...
regards
As of yet I don't know how to get rid of the fish eye lens effect. If I am honest I probably won't anytime soon either as I have a lot to be working on IRL
Could u please tell me how to root,thanks:good:
Nice ROM
Charles-HK said:
Could u please tell me how to root,thanks:good:
Click to expand...
Click to collapse
Hi Charles,
I have not been able to gain root. Initially I thought it was due to the SEpolicy denying root access. However the last few builds have had SEpolicy set to permissive so would allow root. However I am still struggling to even install root. The official Omni line is that all their builds allow for the use of systemless root from Chainfire. They do not support system root which is what is used on the stock Sony derived builds.
If you have any success regarding root please let me know.
mcgi5sr2 said:
Hi Charles,
I have not been able to gain root. Initially I thought it was due to the SEpolicy denying root access. However the last few builds have had SEpolicy set to permissive so would allow root. However I am still struggling to even install root. The official Omni line is that all their builds allow for the use of systemless root from Chainfire. They do not support system root which is what is used on the stock Sony derived builds.
If you have any success regarding root please let me know.
Click to expand...
Click to collapse
Thanks,you can try to make a cm13 build.I know it is not a good idea:crying:
---------- Post added at 11:23 AM ---------- Previous post was at 11:20 AM ----------
mcgi5sr2 said:
Hi Charles,
I have not been able to gain root. Initially I thought it was due to the SEpolicy denying root access. However the last few builds have had SEpolicy set to permissive so would allow root. However I am still struggling to even install root. The official Omni line is that all their builds allow for the use of systemless root from Chainfire. They do not support system root which is what is used on the stock Sony derived builds.
If you have any success regarding root please let me know.
Click to expand...
Click to collapse
You are a good developer, your ROM is the most stable of third party Android M.:good:
Thanks but all praise should go the omni and SonyAOSP teams
Could please post the link (if any) of the config file repo you used to compile the ROM ?
alokhan said:
Could please post the link (if any) of the config file repo you used to compile the ROM ?
Click to expand...
Click to collapse
the platform manifest I use is from OmniRoms github.
https://github.com/omnirom/android
and for the AOSP builds
https://github.com/SonyAosp/platform_manifest
as you will be able to see from these, I am only building not developing. That said I am currently synching up again for some new builds. Sony have released some new a3xxx adreno blobs so camera may be even more stable.

Categories

Resources