For those power users of you I will be putting builds into the testing folder on Android File Host the conditions of using these are:
You give me feedback
You give me logs
You give me complete and proper steps to reproduce an error
You clean flash these I WILL NOT accept logs for dirty flashes, none, zero, zilch, nada
SELINUX MUST BE ENFORCING
THESE BUILDS MAY/MAY NOT NUKE THE SDCARD AND SO FORTH YOU FLASH AT YOUR OWN RISK (generally zero but covering my ass)
I WILL NOT BE HAND HOLDING!
NO GENERAL USER QUESTIONS IN THIS THREAD FOR THOSE GO TO THIS THREAD
I will bump this thread when a new testing is up
EXAMPLE TEMPLATE
Rom date
Bug/issue
Steps to reproduce
Adb log + dmesg/kmsg log
Anything else
DOWNLOAD
Changes that have been done, changed lots of the selinux policies. Device is actually in enforcing mode and no battery hacks.
Let me know if there's any issues with anything.
Logs I want are the following
/data/misc/audit/audit.log <--- adb shell su cp /data/misc/audit/audit.log /sdcard/audit.log
a logcat
and a dmesg
Ok guys, I've uploaded a seperate boot.img to flash with the testing rom.
GPS (device only wifi+data off) outdoors!
Stability of the device
Any other issues. USE THE Template above. Looking forward to the reports.
I won't accept Logs or bugs without the above boot.img being used.
Just flashed rom + the boot. First imp - Apps installing faster and much smoother then before... Will report back after few hours of good usage
Sent from my Lenovo TAB S8-50LC
A new build is uploading. This has a new ramdisk and so on. flash only if you feel brave.
Experimental.zip? I was about to flash the one that you've uploaded last night.
morbvamp said:
Experimental.zip? I was about to flash the one that you've uploaded last night.
Click to expand...
Click to collapse
Don't worry about that one for the minute the experimental one can wait to be tested.
For those of that want to try the experimental builds, just post here and I'll pm the link. Too many people are downloading the test build without the boot.img >.< I can't trust people with the experimental which has it's own boot.img currently.
So far this ROM is the most snappiest 12.1...
Noticed:
Display on takes time when u get a call..
Very rare lag while u use two or more apps
Sent from my One X+
Same as mackhenri here. Flashed rom with separate boot.img. Feels a bit faster than previous build. Confirmed (again) that GPS working with only device.
If I run into an issue, will attach some logs.
Thanks again
Lloir said:
A new build is uploading. This has a new ramdisk and so on. flash only if you feel brave.
Click to expand...
Click to collapse
Have u uploaded the new experimental build already
Sent from my One X+
mackhenri said:
Have u uploaded the new experimental build already
Sent from my One X+
Click to expand...
Click to collapse
Oh yeah it's been there for ages, I've just hidden it because people don't listen and download the boot.imgs, 2mins I'll pm you the link
Cm-12.1 testing
Lloir said:
Oh yeah it's been there for ages, I've just hidden it because people don't listen and download the boot.imgs, 2mins I'll pm you the link
Click to expand...
Click to collapse
Hi Lloir
I also want the new experimental build!
Thanks!!
I've been using the (cm-12.1-20150624-UNOFFICIAL-enrc2b) build and I didn't have any issues at all. If you need me to test some experimental build, send me a pm. And let me know if there's anything specific to test or something and I'll flash it right away!
morbvamp said:
I've been using the (cm-12.1-20150624-UNOFFICIAL-enrc2b) build and I didn't have any issues at all. If you need me to test some experimental build, send me a pm. And let me know if there's anything specific to test or something and I'll flash it right away!
Click to expand...
Click to collapse
Once my current build is done, you can test that.
Exp Rom + Boot.
Battery Life Excellent (never used any other rom with such good battery management)
More smoother then before.
More stable (Perfect - no freeze)
Camera + Gallery - snappier
Only issue is apps takes ages to install but not sure if its me only.
Edit: You have done magic
mackhenri said:
Exp Rom + Boot.
Battery Life Excellent (never used any other rom with such good battery management)
More smoother then before.
More stable (Perfect - no freeze)
Camera + Gallery - snappier
Only issue is apps takes ages to install but not sure if its me only.
Edit: You have done magic
Click to expand...
Click to collapse
The app issue isn't really an "issue" it's due to the way I've set the rom up now. It will dex everything as they are installed, hence the snappier feel and super long initial boot
It's not as if storage is an issue on the device
New build
https://www.androidfilehost.com/?fid=24052804347765765
Things that mostly need testing:
Bluetooth tethering
Stability
Lloir said:
New build
https://www.androidfilehost.com/?fid=24052804347765765
Things that mostly need testing:
Bluetooth tethering
Stability
Click to expand...
Click to collapse
Do we need to necessarily flash the boot inside the ROM zip or it will be fine with the exp boot image..asking cause no access to PC till Monday
Sent from my One X+
mackhenri said:
Do we need to necessarily flash the boot inside the ROM zip or it will be fine with the exp boot image..asking cause no access to PC till Monday
Sent from my One X+
Click to expand...
Click to collapse
Yes, just wait until Monday. It's no big deal.
Related
Take a deep read at http://www.xda-developers.com/android/from-the-bbq-omnirom/
Anyways,here's my build
Build1:
http://www.androidfilehost.com/?fid=23159073880936389
I don't have a device,but would like testers
If it works decently I will ask to have shooteru into the official devices
GPL Compliance:
https://github.com/Evervolv/android_kernel_htc_msm8660/tree/jellybean-4.3 with F2FS changes found in http://review.evervolv.com/#/q/status:open,n,z
Not Working:
Camera(doesn't work fully)
Camcorder
GPS(please test)
3D Playback and recording
Signal Stregth
helicopter88 said:
Take a deep read at http://www.xda-developers.com/android/from-the-bbq-omnirom/
Anyways,here's my build
http://www.androidfilehost.com/?fid=23159073880936375
I don't have a device,but would like testers
If it works decently I will ask to have shooteru into the official devices
GPL Compliance:
https://github.com/Evervolv/android_kernel_htc_msm8660/tree/jellybean-4.3
Click to expand...
Click to collapse
Hello,
can't wait to test this new rom but the download link seems to be wrong for me ... I've checked on you're androidfilehost account and download this from toady in replacement, is that good ? http://www.androidfilehost.com/?fid=23159073880936363
Lyok0ne said:
Hello,
can't wait to test this new rom but the download link seems to be wrong for me ... I've checked on you're androidfilehost account and download this from toady in replacement, is that good ? http://www.androidfilehost.com/?fid=23159073880936363
Click to expand...
Click to collapse
Yes,that file is right
That seems to be a 4.3 Evervolv build. Am I missing something?
The new link is http://www.androidfilehost.com/?fid=23159073880936389
Arbelzapf said:
That seems to be a 4.3 Evervolv build. Am I missing something?
Click to expand...
Click to collapse
I don't think so..omnirom of course is always android and the appearence is similar in every versions..but I think that is a different concept on a programmative side. Finally a real android open-source? read from the link in the first post to know better how does this project consists in (if you really downloaded en evervolv rom, try the link right above my post, it works)
helicopter88 said:
The new link is http://www.androidfilehost.com/?fid=23159073880936389
Click to expand...
Click to collapse
Domenico you are fantastic. Please never leave our evo 3D!!!! Thank's to you we can have the latest versions of wonderful projects like omnirom in a very short time after they are announced. Simply the best!
Well,my evo is gone,and I'm gonna buy a nexus 5(please google hurry up!)
Since hopefully working on the n5 will be boring and not fun as its on the evo I might port 4.4 or whatever comes next
gigsaw said:
I don't think so..omnirom of course is always android and the appearence is similar in every versions..but I think that is a different concept on a programmative side. Finally a real android open-source? read from the link in the first post to know better how does this project consists in (if you really downloaded en evervolv rom, try the link right above my post, it works)
Click to expand...
Click to collapse
Well the evervolv default wallpaper and the evervolv name all across "About phone" led me to that bold conclusion. I'll try the new link now
Arbelzapf said:
Well the evervolv default wallpaper and the evervolv name all across "About phone" led me to that bold conclusion. I'll try the new link now
Click to expand...
Click to collapse
Omnirom for now lacks most customization,it's still a big WIP,and I used evervolv device trees(with my edits,tho)
don't be surprised if it says ev all over the place
helicopter88 said:
Well,my evo is gone,and I'm gonna buy a nexus 5(please google hurry up!)
Since hopefully working on the n5 will be boring and not fun as its on the evo I might port 4.4 or whatever comes next
Click to expand...
Click to collapse
Yeah even me was interested in nexus 5, even if today didn't come out anything from google..but max in a couple of week will be out for sure, let's see :fingers-crossed: of course working on a device AOSP listed is easier (fully working rom, a recent kernel available, bootloaders factory unlocked without nonsense HTC restrictions)..but working on evo 3D gives more satisfaction LoL So now you are developing in a "blind way", I mean without a phisical device..and you roms boot!! I am impressed Good luck for the 4.4 developing , hope to see in future
Rom still isn't bugless,don't send me PMs with bugs,I already know what is broken
Anyways
Little(quite big tho) experiment
Take a read at http://www.linux.org/threads/flash-friendly-file-system-f2fs.4477/
This file system by default is used on motorola moto x and together with @namenlos we found that it delivers better performance also on our little evo.
As (I hope) most of you know,formatting to a different file system requires a set of utils,thus a different recovery and the loss of all of your data.
I didn't find any good reason to make all of you erase all your data,flash a different recovery and running manually format lines,so I came with a different flashing method..
It is more complex than usual and might not work fine(remember,no device,so no testing)
Download https://www.dropbox.com/s/utdclidhbi4yokp/first.zip and https://www.dropbox.com/s/dkj9n7jb8u1i2vp/second.zip and http://www.androidfilehost.com/?fid=23159073880937120 and place 'em on your SD card
tl:dr:
Flash first.zip,once it ends reboot to recovery,wait for it to reboot,boot again to recovery and flash f2fs.zip
Click to expand...
Click to collapse
Here's a little insight
First zip does the following things:
Make a backup of your /data(make sure you have 1.2 GB free on your SD)
Make a backup of your recovery
Flash a custom TWRP made to work with F2FS
And adds a custom openrecoveryscript to tell the special recovery to flash second.zip(ensure you have it in root of your sd)
Asks you to reboot to recovery(please do it)
Click to expand...
Click to collapse
Once you reboot,custom TWRP starts,reads the script that tells it to flash second.zip
Second zip does the following:
Format as F2FS /data and /cache
Restore your data
Restore your recovery
Reboot(you should then pull the battery and reboot to recovery)
Click to expand...
Click to collapse
From your recovery,flash "f2fs.zip" which is the rom itself,reboot and enjoy
NOTE:
Kernel is not evervolv,it's a hybrid between a old johnnyslt with tweaks,new EV and my various changes
https://github.com/helicopter88/android_kernel_htc_msm8660/tree/jellybean-4.3
Oh yes fantastic file system on the moto x huge gains in performance for a dual core processor, battery performance is unbelievable, 5 hours screen time and you'll still have power left over, loving mine
Sent on my Moto X
I am willing to test it but one thing prevents me from doing that (apart from a lack of free time). How do I get back to the standard FS? do I just restore the backup i would create in the recovery?
decemberhayes said:
I am willing to test it but one thing prevents me from doing that (apart from a lack of free time). How do I get back to the standard FS? do I just restore the backup i would create in the recovery?
Click to expand...
Click to collapse
It doesn't work,no need to try
in that case I am waiting for another build. I will be happy to test it
To go back to the old Rom you might have to restore the recovery first. Just go into fastboot usb mode and flash the official recovery. Then you can restore your backup comfortably in TWRP for sure. IIRC it should also work on the modified TWRP, at least when I tested it.
+1 for the ROM,
would love to see ION kernel and working Camera,
like in Dastin's CDMA Kernels.
milestone97 said:
[…]would love to see ION kernel and working Camera,
like in Dastin's CDMA Kernels.
Click to expand...
Click to collapse
What lead you to those false assumptions that there is a AOSP Kernel around with ION and camera working (for Sensation or Evo 3d)?
http://www.androidfilehost.com/?fid=23203820527943749
Special package here,it's a secret + secret changes package,it's not omni,but if it boots you'll have fun
Now I'm curious ;D
This kernel will be kept simple and inline with stock and free from buzzfree stuff..as the aim is a stable day-to-day use kernel..this kernel is NOT for those who want to break records..as i do not believe and rely on benchmarks..(its me..)
Disclaimer:
i nor xda would be at fault if something weird beyond my test results happen to your phone..also this is not a benchmark kernel..if you like crunching numbers and breaking records go use another kernel..this is meant to save juice and be efficient and stable as a daily driver for Samsung based ROMS..
Features:
- Based on i9205/i9195 source from Samsung OSRC(Thanks for the borked source)
- Fixed a few things left by Samsung to be broken
- Simple and no fancy stuff thats gonna bork your phones..more stuff does not guarantee it's better..
- User voltage control from faux123 for Krait CPU's..
- EXFat support(by Samsung OSRC..)
- OC(if already stable)
- will populate more as things get stable
- Selinux permission is set from enforcing to permissive via ramdisk
- insecure boot image
- Disabled Rooting security measures implemented by Samsung..
Pre-requisites
- Install busybox via CWM or via Playstore before installing my kernel..this is to make sure init.d and also some scripts work properly..
Downloads here: Test build 5(ML1 Ramdisk)
My git: source
Credits:
- noone in particular but thanks to ALL the wonderful devs here in XDA..
If you like the builds please help me get a Soda/pay bills..or the least is just hit the Thanks Button..
one more in case..
uploading..
please report/feedback on any issue you might encounter..please do provide logs(last_kmsg, logcats, dmesg...etc..) so that i can shoot things out..i do not own the device yet and surely things can go wacky along the way..
TIA
kindly someone report if the build boots up..
What do you mean with those features?
- Fixed a few things left by Samsung to be broken
- Removed most of the crappy and buggy stuff..
- GPU Idling fix..
Click to expand...
Click to collapse
I cannot see them on your sources
Grarak said:
What do you mean with those features?
I cannot see them on your sources
Click to expand...
Click to collapse
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
kairi_zeroblade said:
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
Click to expand...
Click to collapse
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Grarak said:
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok so if it bothers you then i will ninja edit it then..its just a general template i used on my previous OP..dont be so harsh on me..
update: edited it to "fit" your standards.. (what a way to welcome me here........now i can go to bed..and get my beauty sleep.. )
update: good morning guys!! any reports or comments if it boots up?? need feedbacks so i can start pushing more stuff..
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Silesh.Nair said:
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Click to expand...
Click to collapse
thanks will invetigate the logs provided..can you upload a stock image of the i9200 btw??so i can check if there are specific differences from the ramdisk of the i9200 from i9205..afaik aside from the LTE there should be other differences from them..
re: root it might have been because of the ramdisk i used..can you shift to Koush's superuser??chainfire's supersu has been finicky with my HTC 4.3 update but Koush's never had a glitch..
Thank you very much for the feedback!!
edit: get the SuperUser by Koush here
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Silesh.Nair said:
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Click to expand...
Click to collapse
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
kairi_zeroblade said:
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
Click to expand...
Click to collapse
Attached.
Silesh.Nair said:
Attached.
Click to expand...
Click to collapse
ok nailed down the culprit..will release a new test build in a few minutes thanks Silesh..it seems i was missing a few stuff..
kairi_zeroblade said:
update: new test build here OP updated as well
kindly test and provide feedback so i can push more stuff in..i have to do alot more maintaining also to my git..
Click to expand...
Click to collapse
I am testing my slimkat build. Will flash and let you know in an hour.
Silesh.Nair said:
I am testing my slimkat build. Will flash and let you know in an hour.
Click to expand...
Click to collapse
thank you it seems i made a minor derp..will fix it now..and upload a new kernel.
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Silesh.Nair said:
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Click to expand...
Click to collapse
update: get test build 3 here
kairi_zeroblade said:
update: get test build 3 here
Click to expand...
Click to collapse
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Silesh.Nair said:
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Click to expand...
Click to collapse
ok got it..will switch to the ML1 ramdisk you gave me..will post a new build in a few minutes..
edit: it seems i was messing with the UCNA2 update with SELINUX..thats why i was borking things..i am now using the ML1 ramdisk..
@silesh
new build up..here
Mako based Candy5 build.
ROM
Download
candy5-Release.v1.0.1-20150216-geeb.zip
To flash I recommend using my TWRP 2.8.6 build.
1) If coming from Kitkat or earlier, wipe: system, data, and cache. If coming from an earlier build of Candy5, it might be safe to dirty flash.
2) Flash the Slim Gapps.
3) (Optional) Flash the latest supersu.zip. The ROM includes superuser, but some people prefer supersu
4) Boot and enjoy
AK Kernel:
Download
AK.500.geeb-aosp-11-27.zip
If you're going to use the AK kernel, I recommend flashing UKM and using the Synapse app for kernel settings.
Source:
CandyRoms
ROM Kernel
AK Kernel
Device
Vendor
Credits to kevinjoa for his work on lollipop for the OG, this would have a lot more bugs without him.
no recent task on new build edit:: sorry is working just have to activate it on buttons xD
It's working fine for me so far. Camera isn't important to me, so I could see myself using this after I sell my G2.
New build:
cm-12-20141120-UNOFFICIAL-geeb.zip
Hopefully fixed camera, but need someone to test.
brothaedhung said:
New build:
cm-12-20141120-UNOFFICIAL-geeb.zip
Hopefully fixed camera, but need someone to test.
Click to expand...
Click to collapse
i wiill test
brothaedhung said:
New build:
cm-12-20141120-UNOFFICIAL-geeb.zip
Hopefully fixed camera, but need someone to test.
Click to expand...
Click to collapse
Literally in the middle of flashing 11/19 build right now. You think I can dirty flash 11/20? Would like to test that for you.
Digil said:
Literally in the middle of flashing 11/19 build right now. You think I can dirty flash 11/20? Would like to test that for you.
Click to expand...
Click to collapse
Heck ya! Dirty flash away. All I did was change the device files for camera. Sorry for the frequent builds. I want to get this camera working and it's hard to do without a camera.
brothaedhung said:
Heck ya! Dirty flash away. All I did was change the device files for camera. Sorry for the frequent builds. I want to get this camera working and it's hard to do without a camera.
Click to expand...
Click to collapse
Definitely no need to be sorry! Thanks for your work! I'll start dl'ing 11/20 right away (unfortunately, I'm on a painfully slow connection right now).
working camera tested on google camera dirty flash
good!oo
Sent from my Optimus G using XDA Premium 4 mobile app
samuel3mn2 said:
working camera tested on google camera dirty flash
Click to expand...
Click to collapse
Same hur, and thanks for fixing the close recent apps fc bug
EDIT: Some reason can't get root acccess on Titanium Backup,flash the SuperSu from your link, will investigate.
NVM, I guess its a TB issue with Android 5.0 >.<, downloaded new version and it works
brothaedhung said:
Heck ya! Dirty flash away. All I did was change the device files for camera. Sorry for the frequent builds. I want to get this camera working and it's hard to do without a camera.
Click to expand...
Click to collapse
will you please tell us which files you changed for camera ?
or link us to commit, plz..
RohanAJoshi said:
will you please tell us which files you changed for camera ?
or link us to commit, plz..
Click to expand...
Click to collapse
I just pushed it to my github now that I know it works. These two commits:
https://github.com/brothaedhung/device_lge_geeb/commit/0e513b01cbc7fecca6414f3ce660c583607f6fb5
https://github.com/brothaedhung/device_lge_geeb/commit/352eb9a37df35a16b7044a60181f8a332e485f20
It had to do with an AOSP update from earlier today that I hadn't merged to the device repo yet and me accidentally deleting a line when merging the 5.0 mako update.
brothaedhung said:
I just pushed it to my github now that I know it works. These two commits:
https://github.com/brothaedhung/device_lge_geeb/commit/0e513b01cbc7fecca6414f3ce660c583607f6fb5
https://github.com/brothaedhung/device_lge_geeb/commit/352eb9a37df35a16b7044a60181f8a332e485f20
It had to do with an AOSP update from earlier today that I hadn't merged to the device repo yet and me accidentally deleting a line when merging the 5.0 mako update.
Click to expand...
Click to collapse
thanks limit exceeded..
downloading now..
thanks for all effort..
Camera force closes.
I flashed all the files you provided according to the instructions and everything works except for the camera, I get a black screen then force closes. And there are 3 small bugs: one is on screen>advanced settings I press that option and it doesn't do anything, the other had something to do with the network settings but I forgot what was the problem, sorry. And the last one is that I can't activate the battery saver (maybe that's not a bug, I don't know.) But it's a great ROM overall
brothaedhung said:
New build:
cm-12-20141120-UNOFFICIAL-geeb.zip
Hopefully fixed camera, but need someone to test.
Click to expand...
Click to collapse
Is SD card working here?
it's OK......
Sent from my Optimus G using XDA Premium 4 mobile app
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
it's a great rom!!!
Sent from my Optimus G using XDA Premium 4 mobile app
AntonyOrtega said:
I flashed all the files you provided according to the instructions and everything works except for the camera, I get a black screen then force closes. And there are 3 small bugs: one is on screen>advanced settings I press that option and it doesn't do anything, the other had something to do with the network settings but I forgot what was the problem, sorry. And the last one is that I can't activate the battery saver (maybe that's not a bug, I don't know.) But it's a great ROM overall
Click to expand...
Click to collapse
Ok, just dirty flashed 11/20 over 11/19. SD card, WiFi, NFC all appear to be working. I can't check mobile data/calling right now, though. Camera seems to be working fine on this one! (oddly enough, though, I can only activate Camera from my lockscreen because it doesn't show up in the app drawer, maybe I have it hidden) Only small thing, as mentioned above, is Settings > Display > Advanced Settings doesn't do anything. Not sure if this is only this ROM, or something related to CM12 in general. Battery saver, however, does seem to work for me.
Thanks again for the work, brothaedhung! This is already DD material for me. I'll test out the battery life over the next few days, and report back. Looking forward to more from you, particularly as the CM team implements more features.
Edit: One more minor thing. Even though I have Location Services turned off, the icon still appears in the status bar.
Rom fully working, but very fast buttery drained, i am repair from TB 20 apps, 1 reboot and my battery lasted for ~1h, deviec hot, i install Trickster mod uc to 384-1,1ghz(device laggy)
and yet noticed, when the phone is completely turned off and charging, the error ap watchdog bark detected with green screen
I have not can see the phone memory after repeated flashing(
take screenshot->"Couldnt capture screenshot. Cant take screenshot due to limiter storage space, or it isnt allowed by the app or your organization."
Awesome work! I'm totally forking your device and vendor tree
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png
PS: The anime character "Haruhi Suzumiya" is copyright of its owner
PS: arise fix
Open up a file manager and go to the root folder. You need to have SuperSU installed for this
You'll see a folder called su, go to /su/su.d
In this folder create a text file, label it as "permissive.sh" and put the following code in
Code:
supolicy --live "permissive *"
Then save the file and go to recovery and flash arise and Dolby Atmos addons again and then reboot
It should now work
Stop reading my bs! Here's the download link
https://srv1.botstack.host:8000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
Or
http://srv1.botstack.host:9000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
This is a project that started as a kernel for my ROM and that is what it's going to be
It can be flashed on other ROMs too and I will gladly provide support however I can't guarantee results
Do note that this is a "secure" kernel. It has many of the security patches merged from CAF and selinux enforcing is forced with no way to go to permissive
What about v4a?
Get SuperSU and input these lines in a terminal
Code:
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
allow audioserver audioserver_tmpfs:file { read write execute };"
Wait for a few seconds, swipe away v4a from the recent apps list and launch it again. It should now work
Why isn't a thermal throttling tweak included inside this kernel?
Well in my usage the kernel is so fast that thermal throttling modifications are not needed. You can apply if you want
Currently known bugs?
Nothing
OMG you're copying boeffla!
Relax. I used boeffla's anykernel base as I was in a hurry and didn't have time to make my own zip. Also, boeffla's anykernel zip is one of the best around trust me
What are the features?
Too lazy to write, check back here in a few days but there are quite a lot of features you're gonna like
I'm a nerd, I support the GPL, I'm gonna take you down because you didn't release the source code and neither did you tell me whose toolchain you used!
Bro you need to take it easy
Toolchain: https://bitbucket.org/mdalexca/aarch64-linux-android-6.x
Kernel source: https://github.com/anupritaisno1/android_kernel_oneplus_msm8994_custom
I'll try it when there is ROM with new security patch. Looking forward to it!
NeoVsk said:
I'll try it when there is ROM with new security patch. Looking forward to it!
Click to expand...
Click to collapse
I don't care about other ROMs but I'm actively adding security patches into my kernel's source so relax
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
chxei said:
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
Click to expand...
Click to collapse
Not at all
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
NeoVsk said:
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
Click to expand...
Click to collapse
Known issue
anupritaisno1 said:
Known issue
Click to expand...
Click to collapse
Could you include fast charge in following builds?
NeoVsk said:
Could you include fast charge in following builds?
Click to expand...
Click to collapse
That was my mistake. I forked fast charging from halogenos without realizing that it never worked
This is something I sadly can't fix. You'll have to wait for halogenos devs to update this
Fast charge coming in next build like....
Camera bug fixed!
I don't usually gamble but when I do I buy note7
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
xarisCY said:
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
Click to expand...
Click to collapse
If you start the camera, my kernel fails to turn it off so the camera will be unavailable for use after the first time you use it and you'll have to reboot
I'm working on fixing this bug. Why are you interested in this bug?
Sorry, my mistake. I though was something different.. Sorry
Where can i download naruhi ROM?
Kernel has been updated
All known bugs squashed!
Seems cool but an enforcing only kernel has its downside for me. I'm not sure if arise works with an enforcing kernel, would love to see a permissive version as well.
anupritaisno1 said:
Kernel has been updated
All known bugs squashed!
Click to expand...
Click to collapse
Great job! But I'm still getting only about 700mA when charging
Although the Kernel make the ROM very smooth but it's not battery friendly.
playkish said:
Although the Kernel make the ROM very smooth but it's not battery friendly.
Click to expand...
Click to collapse
On my phone I can't find a difference between my kernel and stock
Also this is a cm kernel. Expect some general battery drain
That being said, I've really worked hard on wakelocks and doze
Hi got your quote on bens kernel page @anupritaisno1, could you explain me more about this kernel. I guess it will break the focus of my camera due to some new commits, etc as bens kernel v5 had done the same to me. Also, as im using bens RR Rom, will this have any bugs or side affects with that rom (i had flashed boeffla kernel and had to face a lot of problems on his rom such as the xposed modules becoming inactive or not performing after some time, etc.) and last main thing, idle battery drain