[ROM][AOSP][DEV][WIP][S4] Unofficial OmniROM 4.4 CLOSED! - HTC One S

Why Omni?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Taken from http://omnirom.org/why-omni/
Screenshots and more info are here
BACKUP YOUR PHONE!!!
* Your warranty was void when you started messing around with your phone.
* These builds are unofficial and are unsupported.
* ONLY YOU AND NO ONE ELSE IS RESPONSIBLE FOR ANYTHING BAD THAT MIGHT RESULT FROM FLASHING THIS ROM!
* Finally Blah Blah Blah good luck!
This ROM probably has the same requirements as any other AOSP 4.4 based rom with the 3.4.x kernel.
Nandroid and then a full wipe.
ROM when its up you can Download Here
PA 0-Day Gapps Get it here
if needed SuperSU 1.75
KNOWN BUGS
Probably whatever is wrong with other KitKat 4.4 roms so...you tell me?
This is based on work done by xHausx for the HTC Evo 4g LTE. You can view the original thread HERE
Thanks
Especially xHausx for the device and common repos and for taking the time to help me get the build process running.
intervigilium for kernel and device repos, because without him most HTC devices would still have Sense
XpLoDWilD, pulser_g2 and all of Team OmniROM
CM for the various repos and for all they've done for the community
XDA:DevDB Information
OmniROM, a ROM for the HTC One S
Contributors
mo976, xHausx
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Abandoned
Created 2013-10-31
Last Updated 2013-12-03

Reserved
NO SD CARD!!!
A fix is being worked on but... NO ETA's

Looks promising. Cant wait to try it.
Thanks for keeping the One S alive.

Gotta try this! Thanks
Sent from my One S using XDA Premium HD app

HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.

nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong

nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
yooouuri said:
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
Click to expand...
Click to collapse
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.

mo976 said:
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
Click to expand...
Click to collapse
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack

Flashalot said:
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Click to expand...
Click to collapse
Well I'm trying anyhow after going through the various dependency files just to double check. I'm hoping it was just a bad build or something so I am pulling down the repo from scratch and hopefully will have a new build in a few hours.
Sent from my One S using XDA Premium 4 mobile app

Looking forward to this
And maybe try the 1.20 radio...

First working build is up try it out let me know!

mo976 said:
First working build is up try it out let me know!
Click to expand...
Click to collapse
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.

nespresso33 said:
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
Click to expand...
Click to collapse
I noticed that but wasnt sure if its a feature or bug...lol it seems to come and go...

If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone

yooouuri said:
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
Click to expand...
Click to collapse
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app

mo976 said:
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/

yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
I will check if that's whats missing. I am not sure how to disable strict mode by default since its a setting. Lock screen delay should be the same as cm since its the same kernel.
Sent from my One S using XDA Premium 4 mobile app

yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.

mo976 said:
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
Click to expand...
Click to collapse
Maby a logcat will give the information you'll need?

yooouuri said:
Maby a logcat will give the information you'll need?
Click to expand...
Click to collapse
I understand what it says but...it may as well be Chinese because I am not any closer. I attached if you want to take a look.

Related

[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies

Team EOS​JB 4.1.1 TF700T​NIGHTLIES​
Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Nightly builds:
Goo.im
Mirror1
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom. Please use these gapps rather than other gapps packages, as we know that this package works.
Gapps package gapps
--
Features:
Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Kernel Note: As with the rest of the GPL sources, the kernel can be found at http://git.teameos.org/eos/kernel/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery.
Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS or JB based rom.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
---
Enabling voice search in google now
Go into Settings
Go to "Language & input"
Scroll down to "Speech" and click on "Voice Search"
Click on "Download offline speech recognition"
Swipe Across to the "ALL" tab if needed
Download your speech pack for your language
hiemanshu is your maintainer for this device.
Known issues:
GPS
Portrait applications
Quick list of features:
Theme manager support
init.d
busybox
SuperSu for root access (can't live without root)
Colour customisation of the clock and statusbar
Soft key long press actions
Custom targets on he navigation key long-press popup ring (Where google now is shown)
Many many more
Nice! Thanks brother
Sent from my Transformer Pad TF700T using XDA Premium HD app
I'll jump in just for fun.
Wow now teameos comes through in a big way. Why haven't I unlocked yet again??
bigrushdog said:
I'll jump in just for fun.
Click to expand...
Click to collapse
hey bigrushdog! Now that EOS is here, I know this tablet has arrived!
My favorite ROM on the Transformer Prime has made the jump. Can't wait to get home and try this. Finally a reason to unlock and root my device.
Now I have a reason to change my stock recovery. Thanks a lot guys.
Sent from my HTC One X using xda premium
What can the CM10 version better than the others that it's here already?
The portrait bug is the one thing holding me back from flashing this. Grrrrrrr!
With the risk of pointing you to something either very stupid or very obvious, or both, the ROM referenced here:
http://forum.xda-developers.com/showthread.php?t=1779133
reputes it has fixed the screen tearing, and enhanced portrait mode (and some not specified fixes to portrait mode). Would it be of use to contact the dev and see what (s)he has been up to?
What about the lag problem with bluetooth headset we have with stock ROM ?
Does it still exist with this ROM ?
And I will maintaining this ROM as well. So contact me for any issues Working on solving the tearing and portrait mode issues
Sent from my Galaxy Nexus using xda app-developers app
bigrushdog said:
I'll jump in just for fun.
Click to expand...
Click to collapse
Mother effer!!! Bigrushdog from miui on the evo 4g? Of so what's the chances of getting miui on the infinity?
Sent from my SPH-D710 using Tapatalk 2
gmfeny said:
Mother effer!!! Bigrushdog from miui on the evo 4g? Of so what's the chances of getting miui on the infinity?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You want me to try that too
hiemanshu said:
You want me to try that too
Click to expand...
Click to collapse
Jesus, what can't you do?
Sent from my JellyBean Burrito (Inspire 4G)
Will this fix the I/O-issues?
i get lots of reboots, to the point of being unusable what has this rom got to offer that cm10/bb/others dont?
Drewman294 said:
Jesus, what can't you do?
Sent from my JellyBean Burrito (Inspire 4G)
Click to expand...
Click to collapse
Sprint faster than Bolt
Can't get the rom to boot. It gets stuck at the Asus logo.
Unlocked ICS bootloader
Twrp 2.2.2.1 the latest.
Fully wiped including data, system, Cache and dalvik.cache
Then installed hiemanshu's cm10 9/14 alpha and boots fine.
And for some strange reason
I can't go into fastboot. It says starting fastboot USB download however don't see the device in fastboot. Just waiting for device. All win drivers are installed. I do see Asus bootloader in device manager.
I was going to erase cache from fastboot just like my hox.
EDIT I'm not sure about seeing Asus bootloader while in fastboot. Have been at this for 5 hours now. So if you ask me my name I probably say Asus bootloader
EDIT2 I think fastboot issue is resolved. Thanks hiemanshu.
Sent from my HTC One X using xda premium
I no longer seem to have access to fastboot either...
MartyHulskemper said:
I no longer seem to have access to fastboot either...
Click to expand...
Click to collapse
fastboot -i 0x0B05 devices try that

[ROM][JB] Beta Testing for AvatarROM - HTC Desire(Bravo)

We are the developers of AvatarROM .
We have upgraded the ROM to JB (4.2.2). Would anyone be interested to do a beta test.
Instructions:
If it's the first time flashing avatarrom or coming from another ROM
Required: Root + S-OFF (STOCK HBOOT)
Required: at least 512MB ext4 sd-ext partition
Download link
Amazon S3
Reboot to recovery
Flash Gapps - http://woh-roms.weebly.com/gapps.html
Feature request page - https://avatarrom.uservoice.com/forums/193652-avatarrom-feature-request
It's official! :good:
Evervolv base?
have to try and give some feedback,thanks for your work,
Great to see you guys here..!!
What's the difference with the Rom that VJ posted here:
http://forum.xda-developers.com/showthread.php?t=2234114
This one already was 4.2.2
Greetz
Just flashed it. The first bug that I noticed is that the sim card probably is not detected as I have no network connection (didn't ask for pin code and manual network selection gives an error).
TimHermans said:
Great to see you guys here..!!
What's the difference with the Rom that VJ posted here:
http://forum.xda-developers.com/showthread.php?t=2234114
This one already was 4.2.2
Greetz
Click to expand...
Click to collapse
We will officially build for Desire from now on and you will receive updates every week.
bippi79 said:
We will officially build for Desire from now on and you will receive updates every week.
Click to expand...
Click to collapse
nice! can you provide a list of things working and not working?
k3lcior said:
It's official! :good:
Evervolv base?
Click to expand...
Click to collapse
Is it..?
Greetz
TimHermans said:
Is it..?
Greetz
Click to expand...
Click to collapse
In kernel section in about phone, evervolv is mentioned among other things, so to cut the long story short, yes.
Another one kanging Nikez/Evervolv...
Bojan155 said:
Another one kanging Nikez/Evervolv...
Click to expand...
Click to collapse
Why that is bad? In my opinion it is better, so everyone can use whatever he wants, that is the meaning of open source.
Ok it may not good too have x1000 cm10.1 roms and x1000 avatar roms (like in gb times), but having 1(or 2) of each rom type is quite good in my opinion.
Tapatalked with my JellyBean powered HTC Desire
MetinKale38 said:
Why that is bad? In my opinion it is better, so everyone can use whatever he wants, that is the meaning of open source.
Ok it may not good too have x1000 cm10.1 roms and x1000 avatar roms (like in gb times), but having 1(or 2) of each rom type is quite good in my opinion.
Tapatalked with my JellyBean powered HTC Desire
Click to expand...
Click to collapse
at least show some respect and credits from the source you reap.
Bojan155 said:
at least show some respect and credits from the source you reap.
Click to expand...
Click to collapse
Yeah thats right, nothing about nikez/evervolv on the first post
Tapatalked with my JellyBean powered HTC Desire
Bojan155 said:
Another one kanging Nikez/Evervolv...
Click to expand...
Click to collapse
OMGz, dey using exizting stuff!
Ok, seriously, this got sooooo childish over time. I really think nikez & the while team are doing an amazing job, fo' sure.
+ They are open source which is amazing.
So, why would anyone really rewrite the whole thing? Just to grow some imaginary balls? What would you do?
The only question is:
If they (Avatar & everyone who uses their sources) improve the existing stuff, do they also release the sources for everyone?
Have a nice day and please rethink your opinion about this and open source in general.
Sure they haven't mentioned Evervolv yet, but I hope they will edit OP soon and match the rules.
By the way, 99% of those you accuse of "kanging" don't even kang, so get your facts right.
Kanging implies that they use Evervolv code (in this case) and don't admit it.
(I don't even mention that they (EV) would be lost without CAF, Google, CM sources etc.)
WoH said:
OMGz, dey using exizting stuff!
Ok, seriously, this got sooooo childish over time. I really think nikez & the while team are doing an amazing job, fo' sure.
+ They are open source which is amazing.
So, why would anyone really rewrite the whole thing? Just to grow some imaginary balls? What would you do?
The only question is:
If they (Avatar & everyone who uses their sources) improve the existing stuff, do they also release the sources for everyone?
Have a nice day and please rethink your opinion about this and open source in general.
Sure they haven't mentioned Evervolv yet, but I hope they will edit OP soon and match the rules.
By the way, 99% of those you acuuse of "kanging" don't even kang, so get your facts right.
Kanging implies that they use Evervolv code (in this case) and don't admit it.
(I don't even mention that they (EV) would be lost without CAF, Google, CM sources etc.)
Click to expand...
Click to collapse
We want to make sure the rom works fine. Once we get confirmation that it works we will make an official post with Changelog , credits etc. We always provide credits to all the people involved.
Sent from my HTC One X using xda app-developers app
bippi79 said:
We are the developers of AvatarROM .
We have upgraded the ROM to JB (4.2.2). Would anyone be interested to do a beta test.
Instructions:
If it's the first time flashing avatarrom or coming from another ROM
Required: Root + S-OFF (STOCK HBOOT)
Required: at least 512MB ext4 sd-ext partition
Download link
Amazon S3
Reboot to recovery
Flash Gapps - http://woh-roms.weebly.com/gapps.html
Feature request page - https://avatarrom.uservoice.com/forums/193652-avatarrom-feature-request
Click to expand...
Click to collapse
HI op if you want the avatar theme to be the theme applied when Rom is booted for the very 1st time add this to build.prop
persist.sys.themePackageName=com.avatar.theme.Denim
Then the avatar theme will be loaded up by default every time the phone is booted up thanks x
---------- Post added at 06:45 PM ---------- Previous post was at 06:37 PM ----------
Not carrying on the rant over here lol but Come on guy's the whole Rom is not evervolv's just because they ported the Rom DONT make every single app or code in the rom theirs. Yes they may have coded SOME things but NOT everything. So what if the OP used most of the current avatar rom he HAS THE RIGHT to because android is OPEN SOURCE. I am fed up with members on xda all they care about is THIS IS MINE NA NA NA NA NA get a grip of yourselve's are you really going to act like a child for a few codes and a few apps ???? My 2 year old daughter would laugh at you for acting more like a child than she is. Come on guy's developers should SHARE not argue and point the fingers at eachother. And if people didnt KANG or whatever the hell you want to call it then where would most of the rom's on xda be ????? Every developer os sense Rom's KANGED HTC do you see them coming on here chucking their dummy's out the pram ???? because i dont see them doing that. I think it is sad it has to come down to developers arguing like children over some damn files when they should be sticking together like a comunity should. This is why most good hearted developers LEAVE xda because the developers are selfish and act like children. That's all i have to say on the matter. Now i tend to my CHILD. Take care xxxx
bippi79 said:
We want to make sure the rom works fine. Once we get confirmation that it works we will make an official post with Changelog , credits etc. We always provide credits to all the people involved.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you for bring it to bravo!
For people who don't know what is avatar, visit their site.
And this one is based on CM10.1 and kernel from evervolv.
Sent from my HTC Desire using xda premium
I don't understand why everyone starts to accuse people of basing their rom on others' source. Isn't that the whole poing of open source and sourse sharing?
This way, google should accuse and sue every single developer for using the Android source.
So lets just enjoy this ROM, and appreciate that there are still people who work for this device.
Okay I tested this rom and I have to say it's fast but 2 bugs : There is no signal ( probably simcard not detected but not sure) , graphical glitches ( everywhere, not only in YouTube app, the screen kinda tears and acts weird, everyone should know what I mean) . I tested it for a while and that's the bugs I found. It's fast ROM but the glitches and other bugs make me to not use this ROM for now.
Sent from my HTC Desire using xda premium

[ROM][4.3] Unofficial OmniROM builds for Nexus 7 (grouper) [MULTIWINDOW][16/10]

OmniROM Unofficial Builds
As you all know, OmniROM has been announced yesterday. This brand new ROM contains a lot of new, exciting functionality. One of these new functions is the multi-window support! Just like ROMs on some Galaxy Notes, or the ancient Cornerstone, you can run two applications simultaneously! Aside from that, the best thing about this ROM is the focus on the community: while the ROM itself is not available yet, the developers behind it really seem to be willing to listen to the community, which is a really good thing.
As the team of OmniROM states on their website:
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. We offer you an alternative to other ROMs that may choose to water down their distribution at the expense of providing options for the user.
Click to expand...
Click to collapse
And the list of features as listed by XpLoDWilD in this topic:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
Click to expand...
Click to collapse
Unofficial builds
However, builds are not available yet. Logically, the ROM probably has not been thoroughly tested yet and that's why they are not building their source on a nightly basis. If you are as impatient as I am, you probably want to get your hands on this ROM as soon as possible! That's why I compiled OmniROM from source, for the Nexus 7 (grouper).
This flashable ZIP has not been tested yet by myself, but it should be OK. Compiled on Ubuntu 13.04 x86_64, completely as-is from the repository of OmniROM. Let me say again that this ROM is not modified by me; it is directly compiled from source and packaged into a ZIP. All credits go to the team behind OmniROM at http://omnirom.org.
Downloads
The builds below will probably be updated about every three days. I recompile from source whenever significant modifications are added to the multi-window functionality.
16/10 (working fine, with multi-window)
custom_grouper-ota-eng.chaoszx.zip (145.9 MB)
https://mega.co.nz/#!yEsHkDSa!PtTVqVPcvFY3FqP20M-1Vnq87rkVMPKJJ4aPuJA0IH8
14/10 (does not boot):
omnirom-4.3-20131014-NIGHTLY-grouper-unofficial.zip (138.7 MB)
https://mega.co.nz/#!HVF3DDAY!FveJvAE2Wffm2WNcezemTAwHYAleOKf13-zg82cZ118
Thank you
If you appreciate the time I spend to compile these ROMs from source for you, a donation would be appreciated as it would cover a bit of my expenses on power. Aside from that, I am hoping to save some money before I go to university next year, so any donation is much appreciated! PayPal donations can be sent to [email protected]. Thank you in advance for your support.
Notes
Multi-window can be activated by opening an app. Then go back to the launcher by pressing Home. Load up another app. Press the Multitask button, long-press the app you opened previously, and hit 'Split View'.
The Back button is not working at boot. To fix it, go to Settings > Language and Input > Default (under Keyboard & Input Methods) > Google Keyboard. The force closes of the AOSP keyboard won't happen now, and your Back button will work fine.
Reserved.
Reserved as well.
Flashing failed :/ Will try again.
Hypercaine said:
Flashing failed :/ Will try again.
Click to expand...
Click to collapse
Hang on, I am about to flash it on my Nexus 7. If it doesn't flash, I'll check what's wrong and fix it within an hour
Flashing right now, this is gonna be great!
Sent from my SCH-I535 using xda app-developers app
FAILED
set_perm: some changes failed
E:Error executing updater binary in zip ´/sdcard/
Error flashing zip
Same problem here
Confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
chaosz-x said:
confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
Click to expand...
Click to collapse
f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...
The issue with the flashing is resolved. Before uploading the new ZIP, I am investigating the ROM itself. Check back in about an hour at least
Eagerly waiting
Sent from my Nexus 7 using XDA Premium HD app
Chaosz-X said:
Check back in about an hour at least
Click to expand...
Click to collapse
This looks suspiciously like an ETA, if I ever saw one...
When installing, flashing failed. Also, upload to a site that is android-friendly? Mega is hard for me to use. Maybe mediafire?
Failed for me also.
Sent from my SCH-I545 using Tapatalk now Free
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
podagee said:
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
Click to expand...
Click to collapse
I take it you get a set_perm (status 7 error)? This has to do with the updater script trying to give permissions to a file that doesn't exist, it is relatively easy to resolve. I'll take a look once I get home. BTW, tilapia, mako and flo are probably officially supported, which is why they are mentioned, as this is an unofficial build, it isn't (yet) mentioned
Sent from my Nexus 7 using xda app-developers app
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Chaosz-X said:
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Click to expand...
Click to collapse
FWIW I'm having the exact same problem with my build....it won't boot. Using sources synced as of yesterday morning.
I'm also re-syncing to see if that helps.
Thank you for your efforts! Waiting to try it
God I hate this new ADB system in Jelly Bean. Only allows a logcat if you grant access through Android itself. But when your device doesn't boot, it is impossible to get live logcats atm. Still working on a fix and progress is being made though

| ROM | FLO | AOSP | KitKat | 4.4 | S3 | 11-30-2013

Android 4.4
S3 builds are focused on being a simple, stable, and "stock-like" experience for your Android device.
View the source code at: http://github.com/jakdillard
----------
Developed by:
Jakdillard
----------
Devices currently supported:
Asus Nexus 7 (2013)
LG Nexus 5
S3 includes modifications to extend the basic functions of Android. With each update to Android, S3 features may change to work with the current version.
Feature list:
- Full Google Experience
- Clear Recents with VM Cache drop
- Reboot In Power menu
- Screenshot In Power menu (enable in developers settings)
- Advanced Reboot options (enable in developers settings)
- Swapped "on click" and "longpress" behavior for WIFI, Mobile network, and BlueTooth tiles
- Init.d support
- SuperSU root
Instructions:
First time flashing device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Fastboot oem unlock > fastboot flash recovery recovery.img.
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Known Issues:
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ and Picasa album viewing. Also I DO NOT USE FACE LOCK SO I DIDN'T INCLUDE IT SINCE I BELIEVE ITS A WASTE OF SPACE.
ROM: Link
G-Apps (INCLUDED)
Follow the above link for the complete source to make your own changes or to completely debug down to the core of the rom also follow my github for detailed changes.
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project.
WANT TO CUSTOMIZE THIS ROM READ THIS:
Want to add or remove anything or customize for yourself use DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs.
Hi. Just installed this and I like it. A few others have been having issues with chrome and location services causing soft reboots and really bad stability. This ROM does not have that problem. I tried first with the full PA gapps and had issues with Google search and the Google calendar FC. Wiped and clean installed and used the Banks gapps. All is good now.
Gonna go install the Elemental X kennel now.
Thanks for the ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app
going to try this and add some tweaks to it get more power of using aosp
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
ridobe said:
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
Click to expand...
Click to collapse
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
I have to look over those other roms sources to see what they are missing more the likely they don't have the location services pointing to the right adapter or still using the old way of making device trees causing make to not put the overlays together correctly.
Nice ROM Jak!
Syncing your Repo now!
Update 10-29-2013
http://d-h.st/RlW
10-29-2013
Added Google Play Edition Bootanimation
Added missing Flo props ( sound should be a little better )
Added missing proprietary DRM
De-Odexed ROM
Update 11-3-2013
Well there a beta quality build of KitKat in the op this will not be a daily driver until I have a complete source to work with and proper proprietary binaries but good luch and enjoy. Also consider this a nightly project as features will slowly be added.
Always under the radar for some reason, but your builds are always fantastic. Great job as always on 4.4. Loving the additional features.
Update 11-6-2013
http://d-h.st/bjj
New update but still no camera
jakdillard said:
http://d-h.st/bjj
New update but still no camera
Click to expand...
Click to collapse
Changes?
dictionary said:
Changes?
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 7 mit Tapatalk 4
dictionary said:
Changes?
Click to expand...
Click to collapse
I know he added a file manager and volume rocker wake. Those two weren't in the OP for the first build.
Sent from my Nexus 7 using Tapatalk 4
Unfortunately flash fails inTwrp 2.6.3.1.
Awesome. Best KitKat ROM of all I have tried so far. Smooth and no fc or other issues at all so far. Stable in tests that other ROMs have failed. Thank you!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Mindrocket said:
Unfortunately flash fails inTwrp 2.6.3.1.
Click to expand...
Click to collapse
I believe twrp has updated to 2.6.3.2
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
Every last person using any 4.4 with the new Google Experience Launcher.
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
I just double tap the home button. It's less annoying.
Love Jack's creations. Keep up the great work and thanks for sharing.

How to Get Camera Working with PAC-ROM 4.4.4

This a work in progress. Any help will be appreciated.
The problem:
When I try to Start Camera, I get an error "Can't connect to the camera."
I get the same error from HD Camera Ultra and Focal
Unsuccessful fixes tried and notes of caution:
After installing CMFix for Camera from play store, the app does not seem to do anything at all.
Flashing,
Using TWRP to flash camfix.zip causes phone not to boot up. Had to reflash ROM.
This post is a work in progress, and will be updated as I keep trying until it is an explanation.
The ROM installed these two files in \system\lib\hw
camera.msm8960.so
camera.vendor.msm8960.so
I tried renaming these to:
old.camera.msm8960.so
camera.msm8960.so
I then tried renaming them to:
vendor-camera.msm8960.so
camera.vendor.msm8960.so
none of these worked.
Since the specs of the RAZR M and and the XT897 are very similar, I plan to try these Motorola camera apk's. The RAZR M's front facing camera is lower resolutin; so, I would imagine mine might not work.
If you are running a xt897 build on a RAZR M, that might explain the camera issues...
Are you using the old unified builds? Is there any reason you're not on CM13? PAC hasn't gotten any new builds, unified or otherwise, for a long time (for this device).
arrrghhh said:
If you are running a xt897 build on a RAZR M, that might explain the camera issues... Are you using the old unified builds? ...
Click to expand...
Click to collapse
My phone is an XT897, not a RAZR M. My Photon had already been updated to Jelly Bean by Sprint when I bought it. I am currently running: [ROM][OFFICIAL][KitKat 4.4.4][moto_msm8960_jbbl] PAC-ROM 4.4.4.RC-2. This is a unified build for phones with msm8960 cpu and is based on CM11.
arrrghhh said:
... Is there any reason you're not on CM13? PAC hasn't gotten any new builds, unified or otherwise, for a long time (for this device).
Click to expand...
Click to collapse
I have a CDMA XT897 -- no SIM Card. CM10 is the last release for my device. There are some CM11 Nightly builds available.
Since the XT897 only has 1GB of RAM, I thought KitKat would be a good place to be. This PAC-ROM was the only KitKat 4.4.4 ROM I could find for my phone that still has a live download link.
Everything is infinitely more responsive on all things. The most noticeable is the keyboard. On JB stock ROM, I have to hold keys about 1/4 of a second before the letters show up on the screen ... and just to make it more annoying , if I don't release it precisely when it is registered, I end up with multiple characters, grr. With this PAC-ROM, they are instantly registered.
Also, I can't begin to tell you how many "features" of Android I disable regardless of version:
My wallpaper is a plain black png.
The annoying google search box on my desktop -- GONE!
Screen rotation -- disabled.
The cutsie battery and wireless icons are now numbers.
All animations are disabled.
The list goes on... LOL
That being said, I do wish I had a way to patch my ROM for known security holes in KitKat 4.4.4 now and in the future without having to replace the OS and re-tweak it back with all the changes I want. I use Firefox 40.0.3 for much the same reason .
RandyB201 said:
My phone is an XT897, not a RAZR M. My Photon had already been updated to Jelly Bean by Sprint when I bought it. I am currently running: [ROM][OFFICIAL][KitKat 4.4.4][moto_msm8960_jbbl] PAC-ROM 4.4.4.RC-2. This is a unified build for phones with msm8960 cpu and is based on CM11.
I have a CDMA XT897 -- no SIM Card. CM10 is the last release for my device. There are some CM11 Nightly builds available.
Since the XT897 only has 1GB of RAM, I thought KitKat would be a good place to be. This PAC-ROM was the only KitKat 4.4.4 ROM I could find for my phone that still has a live download link.
Everything is infinitely more responsive on all things. The most noticeable is the keyboard. On JB stock ROM, I have to hold keys about 1/4 of a second before the letters show up on the screen ... and just to make it more annoying , if I don't release it precisely when it is registered, I end up with multiple characters, grr. With this PAC-ROM, they are instantly registered.
Also, I can't begin to tell you how many "features" of Android I disable regardless of version:
My wallpaper is a plain black png.
The annoying google search box on my desktop -- GONE!
Screen rotation -- disabled.
The cutsie battery and wireless icons are now numbers.
All animations are disabled.
The list goes on... LOL
That being said, I do wish I had a way to patch my ROM for known security holes in KitKat 4.4.4 now and in the future without having to replace the OS and re-tweak it back with all the changes I want. I use Firefox 40.0.3 for much the same reason .
Click to expand...
Click to collapse
You're mistaken. The division to separate xt897 cdma (xt897c) and sim modified xt897 gsm (xt897) builds at the time of cm10 was artificial, caused by broken world phone support in cm10 at the time.
The separate cdma and gsm builds were later unified again under a single xt897 cm11 build meant for both cdma and gsm networks as soon as the world phone support was fixed.
xt897 cm-11.0, cm-12.0, cm-12.1 and cm-13.0 builds are supposed to work on cdma networks just fine.
That being said, it's still true that I'm able to test only the gsm stuff myself and the dealing with possible cdma issues solely depends on detailed reports and logs from cdma users.
cm-11 builds for xt897 are here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
cm-12.1 and newer builds for xt897 are here: https://download.cyanogenmod.org/?device=xt897
kabaldan said:
You're mistaken. The division to separate xt897 cdma (xt897c) and sim modified xt897 gsm (xt897) builds at the time of cm10 was artificial, caused by broken world phone support in cm10 at the time. The separate cdma and gsm builds were later unified again under a single xt897 cm11 build meant for both cdma and gsm ...
Click to expand...
Click to collapse
In this case, I am happy to be mistaken! :cyclops: Unless someone knows something I do not, the XT897 is the only qwerty phone that works on Sprint's 4G LTE CDMA network.
I have 2 functional XT897's here. Both are rooted. One has stock JB. The other is currently running PAC-ROM. I use TWRP for recovery and backup, etc.
kabaldan said:
cm-11 builds for xt897 are here: https://download.cyanogenmod.org/?device=moto_msm8960_jbbl
cm-12.1 and newer builds for xt897 are here: https://download.cyanogenmod.org/?device=xt897
Click to expand...
Click to collapse
Since you provided both links, you have me wondering, do I need to install 11 before installing 12.1 or later?
RandyB201 said:
Since you provided both links, you have me wondering, do I need to install 11 before installing 12.1 or later?
Click to expand...
Click to collapse
You can go straight to CM13 if you desire. Just need to be unlocked with a custom recovery (IE TWRP).
arrrghhh said:
You can go straight to CM13 if you desire. Just need to be unlocked with a custom recovery (IE TWRP).
Click to expand...
Click to collapse
Thank you. I flashed cm-12.1-20151007-SNAPSHOT-YOG4PAO339-xt897.zip
Unless, I am mistaken "Snapshot" suggests a more stable / proven / debugged version, is that not correct? That is the highest version with Snapshot on the page you sent me to.
I have been playing around with it this morning. I have 2 xt897's here. Right now, one is running stock JB rooted and majorly tweaked, lol. It is the one I have active with my phone service. So, I can't test SMS or phone calls on the new ROM yet.
Wifi is working. Bluetooth turns on and works with my speaker. Both of the Cameras work, and the software lets me save pics to my exfat formatted sd card with no extra app -- NICE!
I found one problem, but I am not sure how to deal with it. The space key on the hardware keyboard is not working. Can you help me debug that? Or tell me where I should post / ask the question, even?
Thank you again!
RandyB201 said:
I found one problem, but I am not sure how to deal with it. The space key on the hardware keyboard is not working. Can you help me debug that? Or tell me where I should post / ask the question, even?
Click to expand...
Click to collapse
Post in the thread relevant to that ROM, or make a Q&A thread about that topic... but that sounds like a hardware issue.
arrrghhh said:
Post in the thread relevant to that ROM, or make a Q&A thread about that topic... but that sounds like a hardware issue.
Click to expand...
Click to collapse
sadly, you were correct. That key is now dead in all ROMs. :crying:

Categories

Resources