Related
CM 7.2.0 Android 2.3.7:
CyanogenMod 7.2.0 port for FIH FM6 varaints.
Working:
USB
Sensors(partially)
GPS
Audio
Camera(partialy)
Wifi
OpenGL/graphics
Video Playback
Bluetooth
RIL
Bugs:
1) Front Camera is not working
2} Main Camera Zoom is not working for higher resolutions.Works upto some extent for QCIF
3)Portrait orientation is not proper.Some apps run upside down
4)Device suffers from very rare reboot due to kernel panic
Download Link:
ROM:
Code:
http://goo.im/devs/mb-14/viewpad7/cm-7-viewpad7.zip
GAPPS Package:
Code:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Installation:
Boot into CWM 5.0.2.8 recovery
Wipe DATA and Dalvik Cache
Flash ROM
Flash GAPPS package
For DEVS:
Here is my device config:
Code:
https://github.com/mb-14/android_device_viewsonic_viewpad7
Any help will be appreciated.
BUG REPORTING:
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt.
Alternatively, if I ask for a radio logcat, this is the command: adb shell logcat -b radio -d >c:\logcat-radio.txt. Copy and paste this log to pastebin.com, and provide the link.
Send all this information to my email ID:[email protected] with subject as CMBUG
Credits:
CyanogenMod Team for their awesome ROM.
Goo-inside Team for providing their build server
Please donate to these people
Plea for help:
This project would not have been possible without the help of Goo-inside Me Team.
Now they require financial help for upgrading their servers.Please donate to them!!!
For more info check out their website: http://goo.im/
I am eager to test this beta build, and in anything i can help you with... im using a viewpad 7
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
WOw!!! I'm waiting.
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
Non-working functions are due improper implementation of hardware drivers(working on it)
Right now ill be commiting changes to the device config but due to hardware limitations
it takes lot of time to compile a build.
If you have sufficient hardware resources(RAM,space,cores)
you can clone my repo ,download and build the Cyanogenmod source and test it on your phone
PM me for any queries
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
+1, same here, can help debug the issues and work with adb.
Maybe an Irc channel for quicker contact?
cant wait for this. very willing to test
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
I'm think cause 2.3 and 2.2 have most possibility to use in stable. Viewpad 7 is to old to play around. And if this device have rom that can use maximum hardware's can do and stable. I think maybe we can see Viewpad7's ICS ROM in real life.
Sorry for my weak english.
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
Tnie device seems too weak for ics, its a single core 600mhz armv6 CPU.
ics think it wil work on oure device it`s been ported too the x8 to and that`s a arm v6 600 mhz to,
but im happy with 2.3.7
Well, as long as I get 7.1 I'm happy. I still think having it ported is one thing but having it work flawlessly for everyday use is another.
Is wifi working yet? I've seen some commits on github but haven't seen any updates to the update.zip file in the first post.
*edit* where is the update.zip, exactly? Can't seem to find it on the first post anymore
Also, the sensors readout for screen orientation should be somehow flipped or mangled, for by default the device seems to be in landscape mode and if turned to portrait, it flips upside down for me.
hi
really appreciate you looking into porting this to the viewpad/variants etc
hope it goes well, looking forward to a little added ooompf,
(though [ROM]EUViewpad7 v1.7b has been great too)
@googlehome how's the progress?
@anyone I'm a programmer but i'm new to this android build compilation etc. Could anyone point me to tutorial or manual on how to these and those? Thx.
Yes, viewpad 7 seems to weak for ICS... We didn't even get honeycomb (3.X)
Dear Santa...
I'll be happy just with 2.3 and using my front camera with skype or gtalk...
Happy Holidays
Thank for hardwork
Hi
I think Gingerbread is perhaps as far as this device will go - in terms of functionality and "useablilty" - sure I'm sure ICS will "go on" if attempted but i'm pretty sure will fail to be useful (and if someone proves me wrong then I still win as I'll use it)
anyway keep up the good work with this gingerbread attempt - I'm hoping it goes well
Any news for the new year?
Hey Guys, I tried flashing Oxygen 2.3/2.4 several times after full wipe but everytime when I tried to install an app, it freezed my phone and when restarted, all /data apps were gone :/ ... This problem probably occured only to me.. Also I found CM nightlies much stable but sometimes bluetooth didn't work properly and camera exposures were a let down ....
After this, I really found a need to make a fully stable ROM for myself.
That's why I've modded Oxygen V1.1 by popdog123 for my personal use and If you guys want me to share it with you all then please tell..
Things I've fixed are-
1.)Fixed poor quality radio bouttons.
2.)Fixed poor quality spinner(which appears for waiting).
3.)New baseband support.
I know that newer version is fully stable(except for me) and probably has no bugs, but still If you guys want the link for fully stable and bugfree v1.1 ROM then tell me, I'll upload it
I suggest you post the suggestions/fixes in popdogs thread so he can use them to improve it
_Arjen_ said:
I suggest you post the suggestions/fixes in popdogs thread so he can use them to improve it
Click to expand...
Click to collapse
You are by far the most usefull person here, by both mental support and developement
Sent from my LG-P500
@Arjen- I would have done it earlier but, he has already denied developing the .32 version ...
Up to date as of November 22, 2013.
Modified: Installation guide: V2.0, some other parts including general info, changelog etc.
Added: Swapping guide, quick V2.1 guide, quick updating guide
---------------------------------
Are you experienced with ULTRA B.U.X? Please help me write its own guide (PM me)
---------------------------------
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
-------------------------------------------
Did this guide help you? Please hit the "Thanks" button
________________________
Member of Bada Israel
Are you Israeli? Wait for the Hebrew translation
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Retrete said:
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Click to expand...
Click to collapse
That's right. I think I confused it with my GPU thanks for the heads up.
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Kiboi said:
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Click to expand...
Click to collapse
Its all ready activated
Nadavs10 said:
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
Click to expand...
Click to collapse
Thanks Nadavs10, I think a FAQ is a good idea ... the point is how to ensure every newbie reads it before posting ...
I think it would be nice to join or at least to link this with another FAQ it was started in badadroid project page http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions
Some comments:
Does it work for Wave II? YES! Many people ask over and over again the same question. Voice calling works now for Wave II too. If there’s something that isn’t the same for both devices, I will write it.
Click to expand...
Click to collapse
Bluetooth works in S8500 but no in S8530 (see status and this post)
Is it legal? Everything is legal except gapps. Decide for yourself.
Click to expand...
Click to collapse
Both badadroid and gapps are "legal", the difference is licensing model, so developers share badadroid open source code and binaries based in other open source code (android, aries ....) but they do not share gapps as it is google propietary. It is not ilegal to install gapps, but it should be ilegal to include it in badadroid package without google permision, so you have to install it separately.
There are many ROMs like Nand/LS Smook/moviNand. What are these, and what’s the difference? I’ll tell you the truth, I don’t really understand it. If someone knows it would be great for some comment here."
Click to expand...
Click to collapse
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
hunktb said:
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
Click to expand...
Click to collapse
Tigrouzen's rom is based on AOSP (Android Open Source Project) wich is basically, a build of the vanilla android sources released by google and the others implicated in the Android primary developement. (even if, tigrouzen included in his rom some code from CM to allow a better customization of the ROM, and so, it's a little bit different from pure AOSP)
Cyanogenmod is a modified open source android rom... it have some major changes in the code itself (compared to AOSP), in the library it uses, etc... it allow a higher personalisation of the UI than the original AOSP rom. (see their official website to find more info about the cyanogenmod project...)
And I would finally said that yes, tigrouzen's rom is released with an high optimisation care (resulting in a really smooth rom) while volk's rom: works on both wave I and II, I would say that it is a little bit more stable (but that's mainly because it's less often udated, several tigrouzen's updates resulted in an broken functionality (see the bluetooth problems in the AOSP thread) wich he quickly fixed anyway.) and I would say (except for the last "mic in call" update) more "hardware development" oriented (that's just my feeling, but it seems to me that volk (and rebellos) are focusing on the perspective of bringing a fully working android sytem to the wave rather than on the optimization of their existing incomplete system. (and honnestly, it's not a bad thing, it keep general development ongoing)).
Weird
Tigrouzen said:
Its all ready activated
Click to expand...
Click to collapse
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
ghanii said:
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
Click to expand...
Click to collapse
I solved this problem by removing then reinstall the sim, try
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
Thanks i am trying it right now....the ROM and Kernel which I mentioned are the right versions?
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
Try with another sim and tell me if it works
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
GreekBlood said:
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
Click to expand...
Click to collapse
I should move the sim to the top right corner? :/
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Its possible if its old sim, then try get new revision of your sim.
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Go to setting and below bluetooth there is an option of more click on it and then tick use only 2g network
this may help
Maybe "we" collect different external Links in different languages...
Today I saw again German user asked...
Or maybe "we" could use 1 Guide and translate in different languages...
For instance:
English
German
Hindi----> user kktkaran has enough time and energy to do this, instead spxm
.
.
.
Btw.
For few things Screenshots or Video maybe helpfull.
And please, maybe here on XDA 1 copy for reading... So if external Link changed/removed/... it is possible to read here something in Thread.
Thanx in advance.
Best Regards
Tigrouzen said:
Its possible if its old sim, then try get new revision of your sim.
Click to expand...
Click to collapse
i tried a different kernel and it worked fine ver 3.0.85... voice is also clearer. thanks for your help
i am from those people who have problem in wave2 battery like
after restart battery drains to zero or similar level
random shut down problem
so
i have done an experiment which help me thats why i'm sharing it
first of all these problems are because of battery as i think so
1.first remove the battery
2.spin on flat surface if it spin then you can do nothing but replace your battery
3.if doesn't spin check its point of connection and remove any dust or rust
3.last but not least if any thing doesnt work
then
take a "soledring ion" and solder each connecting point of your battery seperately dont let them touch each other so that solder cover connecting points.
now put your battery in phone and test it work or not i.e. your problem solved or not
sorry for bad english
and do it on your own risk and carefully
Asop or badadroid
I'm currently using the ASOP NAND ROM created by Tiguorzen, however it has some call problems similar to old badroid ROM so I'm wondering whether I should shift to badroid project as it seems to get regular updates and ASOP ROM seems like abandoned by tigo(hope not) but ASOP is undobtly the fastes and most streamlined ROM not sure abouy the latest badadroid though.
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
Custom OxygenOS OneplusX - COSX ROM
Intro
First of, I'm not a developer. I'm just a guy who put a couple of things together. I'm a bit above noob-level, so dont excpect high end stuff like some prestigious developers. That being said, I have put this ROM together because of the lack of ROMS based on our original software for the OneplusX. Don't expect to much, the most things happen under the hood. So no shiny backgrounds or boot screens.
Disclaimer
You know the drill, flashing happens under own responsibility. I have tested everything on two devices, and will not put anything online that can possibily harm or damage our device in any way. This being said, if you need support, ask in this thread.
Open Source
The ROM i have created is for the community, which in my opinion also means it should be fully open source. You can edit everything you want. You can use it as base for whatever you like. No need to ask permission or give reference. Seeing the amount of customized original software, I would be happy to see more custom oos roms pop up. No need to put restrictions on anything. Please just don't bother me with antutu benchmark related complaints.
ROM
Now lets talk business
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
perhaps more, cant remember everything
Instructions
1 Obtain Root access and Custom Recovery
2 Download zip file from link
3 Boot into recovery
4 Install zip from sdcard
5 Wipe data and cache
6 Reboot phone
7 Wait for system deodexing (+/- 10 min)
8 Restart phone again
Download
Link will be provided later on
Thanks
- Thanks to everyone buying this phone and making the community what it is today
- Thanks to everyone in the past learning me how to soup a rom together
- Special thanks to Boeffla for providing his kernel and support of integration in this ROM
- If I forgot someone, Thank-you:good:
XDA:DevDB Information
COSX ROM, ROM for the OnePlus X
Contributors
winesh
ROM OS Version: 5.1.x Lollipop
Based On: OxygenOS
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2016-04-04
Created 2016-04-04
Last Updated 2016-04-03
Notifications
- Link will follow in the evening
Changelog
-x-
What's next
- This is version V1. If you have wishes or requests for a future version, please reply. I will see if i can add it in version V2 or upcoming versions.
- Everything is confirmed working. If you by any chance run into bugs, please report them.
So what's different about this rom than stock OOS? I'd give this a shot!
Interesting, I am waiting for the download link and changelog / feature list to give it a go.
Finished compiling, link will be axailable within couple of hours.
@joey24z1 for difference see rom details
@batam for feature list see rom details
Deodexed
Click to expand...
Click to collapse
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
By theming support you mean layers? Or what..?
namquang93 said:
Could you please explain this to me ? I tried google but can't find what is it, and its benefits. Thank you !
Click to expand...
Click to collapse
http://codeversed.com/deodexed-vs-odexed-rom/
Hi. @winesh...
I think placeholder threads are not allowed as per the rules...
However, thanks for your contribution ..looking for download link ASAP
Sent from my ONE E1003 using Tapatalk
I think OP managed to put most of the tweaks one can do to the Stock OOS and created a zip flash package.
IIRC, I did pretty much similar things on my Stock OOS before moving over to CM13.
Good Job OP saving a lot of time for those who want to enjoy the stock experience.
Coud you post a benchmark test?
solidwave643 said:
Coud you post a benchmark test?
Click to expand...
Click to collapse
Did you read the op? Flash the rom and run the test yourself....
Get the link..
winesh said:
ROM details:
Android 5.1.1
Based on OxygenOS 2.2.X
Boeffla kernel 4.0
Pre-Rooted (SuperSU)
Xposed framework
Pre-installed Busybox
Deodexed
Theming support
Zipaligned
Removed software rendering
Heavliy debloated & super slim
Replaced some Google Apps with oneplus Apps
Snapdragon camera (compatible with custom HAL from SultanXDA)
Init.d script support
Some RAM, System and battery tweaks
Updated system Apps
Custom Hardware keys remap
Click to expand...
Click to collapse
Good work :good: Might try this as I kinda liked OOS but I'm currently running Marshmallow and CM based crDroid, so also might not go back to Lollipop
Biggest issues I had with the stock OOS 2.2.0 were:
1. Camera in low light situations. I think it's fixed here with Snapdragon camera?
2. Random rebooting, sometimes few times a day, sometimes few days without. Mostly occurred when playing any game with stock ROM. Is this custom OOS more stable?
3. I could not assign Menu action to HW buttons e.g. long pressing and this led to situation where I had to install Xposed framework and some module to get Menu in Titanium Backup to change backup location to SD card. Is this fixed here with Custom Hardware keys remap?
I know I should test this ROM myself, just pointing out biggest issues I had with stock OOS.
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
coolasnju1993 said:
can u include the stock camera which has manual focus, exposure and iso??? or atleast let me know can i implement the stock oos camera in ur rom cheers
Click to expand...
Click to collapse
Same request here. :fingers-crossed:
Thanks for your work!
So proximity wake up ambient display works in this rom ?
And what type of themes are supported ? Layers or CM ?
Theme support
So OP, You have provided Layers or CM theme engine into rom?
Though Layers supported Stock OOS 2.2.0(Partially not all the themes were working) .
anshu goel said:
http://codeversed.com/deodexed-vs-odexed-rom/
Click to expand...
Click to collapse
I said that deodexed is slower than odex rom. So that means this rom is slower than original OOS right ? Please correct me if I'm wrong.
Waiting for download link...
Will give a shot today...