Develop Bugs

[ROM][29July2013] mROM v4.0 JSS15J - stock 4.3 + GAPPS, MOD(s), etc.

Here is a 4.3 ROM built from AOSP source designed to emulate what a Verizon 4.3 ROM would be like. The changes from AOSP include the addition of GAPPS, addition of Verizon apps, appropriate binaries so everything works, addition of busybox, correct eri.xml, home screen layout to mimic a stock ROM, and the removal of the tethering restriction. The ROM is not pre-rooted, so flash Chainfire's SuperSU if you want root.
As usual, flash at your own risk and post any successes or problems.
Download Link(s) for v4.0: MD5: be4377ab16432112f09d18ae37c91041
DOWNLOAD via Goo.im
Cubby.com MIRROR
SuperSU v1.51 - you may want to check for a more recent version if this link becomes outdated. Flash after you flash the ROM.
Bugs - text-to-speech may not work correctly. Please flash fix attached to this post after flashing the ROM. Thanks AndroJak!
MODS:
Extended Power Menu - CM style
- Ability to reboot, hot reboot, reboot recovery, & reboot bootloader.
- Replaces /system/framework/android.policy.jar
- Thanks to Cyanogenmod and xIC-MACIx
- DOWLOAD
- MIRROR
Thanks to mmuzzy for help building from aosp (fixing t-cdma64 in eri.xml and cell broadcasts menu, plus other stuff I'm probably forgetting), adrynalyne, and djp952 for help building from AOSP.

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
about 5 min or so....
Click to expand...
Click to collapse
first cant wait!!! ^.^

Here we go!!!!!

Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.

Download for 1 server is ready now. I'll get a mirror up as well.
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
Yes, it's working. I asked it how long a bridge was and it read the answer back to me. I haven't done much more than that though yet.

Downloading. Looking forward to this. Thanks Mwalt for sharing!!!
Quick DL as well. 2 minutes has got to be a new record for a JB rom

BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
OP says Google Now is working. I'm downloading now.

excellent. you're a regular johnny on the spot!

downloading now, hope its all good! i'm looking for a "stock jb" style rom of the newest update. ill post my outcome shortly. going to test the basics that are supposed to work.

Is a flash to the JB bootloader recommended? Finally, a build that seems to have all/most components working! No issues with the 4G's or the LTE's?? Lol.
Galaxy Nexus - Slim ICS 4.2

Downloading now. Any thoughts on current JB kernel compatibility?

i wiped data, cache and dalvik cache 2x each, installed and installed trinity kernel on top and hit reboot. (i like trinity for the colors and such, and good battery life ).
first boot took a minute.
updating some apps and gonna test some things.
still getting t-cdma 64 as a carrier

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
DOWNLOAD from Dev-Host
MD5: 8383b87cc2f9e5b510807c3034052ffe
Click to expand...
Click to collapse
Any issues in this build? Also, what are the install instructions?

when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?

^System/media/ringtones maybe?
Galaxy Nexus - Slim ICS 4.2

works well so far. thanks!

xweaponx said:
Downloading now. Any thoughts on current JB kernel compatibility?
Click to expand...
Click to collapse
I've always used stock, so I can't really comment. Now that source is out, I'd expect the JB kernels to work better.
imablackhat said:
still getting t-cdma 64 as a carrier
Click to expand...
Click to collapse
No sure what causes this, but I've never seen it with this build or the previous developer preview build. Did it happen on first boot before you installed anything else?
tycoon177 said:
Any issues in this build? Also, what are the install instructions?
Click to expand...
Click to collapse
I'd recommend a full factory reset, but people can try what they feel comfortable with. Personally, I did a factory reset, wiped both caches, and then flashed the ROM (with TWRP).
imablackhat said:
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
Click to expand...
Click to collapse
Do you have any on your sdcard partition in the Ringtones folder? If not, I'd check \system\media\audio path (subfolders for ringtones, alarms, etc). Delete any duplicates you find in there. I don't have any duplicates and there aren't any in the rom.zip I uploaded.

just overwrote mms.apk in system/apps to get the custom pink mms, and got a quick reboot to my boot screen, this never happened on 4.1 roms that weren't source, don't know if this is normal because i replaced the app and it was a one time thing (i hope). as far as going to system/media/ringtones, i see them but there arent any doubles, however theres doubles when i go to select a ringtone from the menu, for everything system related, ringtones and notifications.

What issues have people had? Any boot issues?

I replaced the "stock" keypress ogg files from ics/jelly bean that sound better with this 4.1.1 release, the new key click sounds are horrible. works fine. i used to have t-cdma 64 with any build from 4.1.1 there is a fix that works that ill just apply. its a xml file or something.

Updating twrp without a pc ?

My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?

Download it on the kindle, flash the zip from inside of twrp, reboot into twrp again and you will notice the version is newer. If you have issues downloading the zip on your kindle just tell me I could temporarily host it somewhere for ya.
Sent from my Amazon Kindle Fire HD using Tapatalk

aakashba1001 said:
My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?
Click to expand...
Click to collapse
you can download HashCode's TWRP Here:
http://forum.xda-developers.com/showthread.php?t=2218802
and install from your current TWRP, just as you flash a ROM.

Thanks guys
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
CM nightly build works good for me, you don't need to wiping new buld everyday, just choise one.
CM team will release a new month build every month, that build will be better than nightly build.
It takes time for the CM team to build a ROM with no bugs, so, just be patient.

I installed the 4/14 unofficial CM11 build that Hashcode posted over in development and am stunned at how well it works! I'll be sticking with this one for the interim. The TWRP upgrade is necessary, but Hashcode made it easy (see link in gatalon's post). In my case, I think it may have even fixed a long standing issue I had.
I've had my kindle HD 8.9" for over a year now, and have always been disappointed with it's performance. Even after I rooted it and put the CM10.1 build on it, it still exhibited weird sluggish, unresponsive behavior. This upgrade to TWRP 2.7 and CM11 has made all the difference in the world. All the weird sluggishness is magically gone.
It was noticeable as soon as I used TWRP 2.7 to wipe everything out. I'm half suspecting I had something wonky going on with the file system that wasn't getting addressed with the older version of recovery. I noticed 2.7 explicitly states that it's calling mkfs during the wipe process where the older version didn't. My uneducated theory is that the older version, 2.6.0.0, just deleted everything where the newer version is actually re-formatting the partitions. I could be way off base though. Just happy it's finally working like I thought a piece of hardware like this should! :victory:

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
No wipe is needed (normally) when updating from one CM official nightly to a subsequent one. It will even detect if the engine has changed and recompile the davlik cache as needed. Personally, I'm a big fan of wiping cache (and only cache) with each new build and I also install any update PA GApps when available ( http://forum.xda-developers.com/showthread.php?t=2397942 ).
Caveat emptor: The CM team makes ever effort to make builds backwards compatible, but always take a backup and be prepared to do a factory reset / data wipe. It very rarely is needed, but you don't want to need a backup and not have one!

If the problem hasn't already been solved, here is an alternative: fireflash. Look it up.
Sent from my Amazon Jem using Tapatalk

AOKP+Nameless+Asylum_Omni

I have tested these roms on my find 7a and they work great. I'm not sure of these will work with find 7 so please do a nand backup and report back in the thread if it works. Credits to the devs for these releases.
Asylum_Omni
AOKP Official Nightlies
NamelessROM Nightlies

Asylum-omni!
That reminds me of my Note 1 days. Deff getting this now.... Is there an asylum thread about?

shure2 said:
Asylum-omni!
That reminds me of my Note 1 days. Deff getting this now.... Is there an asylum thread about?
Click to expand...
Click to collapse
I found the roms by browsing goo.im but I don't think there are any threads for either rom besides this one for now

uppon2 said:
I found the roms by browsing goo.im but I don't think there are any threads for either rom besides this one for now
Click to expand...
Click to collapse
Thanks for sharing. I know Chas has set up a thread or two on XDA before so I'll patiently wait for him to start one up.

Anyone tried this?http://androxfer.in/get.php?p=AOKP-....zip&utm_medium=referral&utm_source=pulsenews
Apparently it works on 7a

I will give it a shot now
Edit* This appears to be the same as the one I linked in the OP but a newer build from Dirk. I am assuming this has now gone in to an official status as I can find it on the AOKP site. OP has been updated with the official site being the link - Thank you for pointing it out as it has now made me realise it was official! - I remember seeing a post from Dirk on Google+ about it being supported but I had forgotten to keep an eye out on the actual AOKP site.
Also added official CM nightlies to OP

Do any of this work with the Find7 (not 7a)?

jampola said:
Do any of this work with the Find7 (not 7a)?
Click to expand...
Click to collapse
I'm not sure. You could make a nand backup then try if you want. I think as soon as there is an AOSP rom built for the find 7 QHD you could use the kernel from that and put it in roms built for find 7a and everything should be fine. Until then it might not function at 100 percent.

Thanks for posting the links dude!
So the AOKP nightly for the FInd 7, that's for the "Find 7" not the 7a? And is it for the 9077? AOKP doesn't specify the device model
Cheers

TheSmokingAndroid said:
Thanks for posting the links dude!
So the AOKP nightly for the FInd 7, that's for the "Find 7" not the 7a? And is it for the 9077? AOKP doesn't specify the device model
Cheers
Click to expand...
Click to collapse
Well Dirk Rettschlag has mentioned it here as the Find 7 but I have used the version displayed in the screenshot from his G+ plus the release on the official AOKP site which also lists it as Find 7 on my Find 7a and it works perfectly. Do a nand backup and have a shot at testing it?

DOES IT WORK?

Find 7 (x9076) compatibility?
Is it compatible with the QHD Find 7?

Anyone having SU issues on the latest Nameless nightly?

JRW 28 said:
Anyone having SU issues on the latest Nameless nightly?
Click to expand...
Click to collapse
What issues are you facing?

uppon2 said:
What issues are you facing?
Click to expand...
Click to collapse
SuperSU kept force closing and was non responsive at all both times I installed the ROM on clean installs. Could get no root features or root apps to work?
I've seen this before as SuperSU needed the binaries updated but I could get no progress with it??

JRW 28 said:
SuperSU kept force closing and was non responsive at all both times I installed the ROM on clean installs. Could get no root features or root apps to work?
I've seen this before as SuperSU needed the binaries updated but I could get no progress with it??
Click to expand...
Click to collapse
Try downloading superuser by clockwork and busybox by Stephen and use those and see how that plays out

uppon2 said:
Try downloading superuser by chainfire and busybox by Stephen and use those and see how that plays out
Click to expand...
Click to collapse
Didn't even think about that. Thanks. Running C-Rom right now as I liked it on my S4. Just getting used to this phone. A big upgrade from the S4!

JRW 28 said:
Didn't even think about that. Thanks. Running C-Rom right now as I liked it on my S4. Just getting used to this phone. A big upgrade from the S4!
Click to expand...
Click to collapse
I liked C-Rom but it gave me issues installing it. Every time I tried to run it it would not pass the boot animation; after 10 minutes of it sitting there the same thing would happen on reboot. The only way I got it to work was by dirty flashing over the top of itself. After installing all of my apps i went to reboot and upon pressing and holding the power button it forced a hot reboot that would not pass the boot animation. I gave up after trying this a few times. I didn't report this to the dev as he has lots of stuff going on.

uppon2 said:
I liked C-Rom but it gave me issues installing it. Every time I tried to run it it would not pass the boot animation; after 10 minutes of it sitting there the same thing would happen on reboot. The only way I got it to work was by dirty flashing over the top of itself. After installing all of my apps i went to reboot and upon pressing and holding the power button it forced a hot reboot that would not pass the boot animation. I gave up after trying this a few times. I didn't report this to the dev as he has lots of stuff going on.
Click to expand...
Click to collapse
Had similar issues first time I tried booting C-Rom. When I seen Nameless on the Oppo forums their instructions added wipe system after full wipe an it seems to be working good like that. I now factory reset, then wipe system, dalvik and cache under advanced and it seems to be working fine like that

JRW 28 said:
Had similar issues first time I tried booting C-Rom. When I seen Nameless on the Oppo forums their instructions added wipe system after full wipe an it seems to be working good like that. I now factory reset, then wipe system, dalvik and cache under advanced and it seems to be working fine like that
Click to expand...
Click to collapse
I have always formatted system. Most roms will have it in the script but I have always done it manually

Slimbean for Locked Bootloaders built from latest sources

Update Posted September 26 2014:
Numerous fixes and additions:
Added Slimbean Extras including Email, Exchange2, Launcher2, Music2 and VideoEditor
Camera delay is positively fixed - absoultely no delay
Removed FM radio which does not work
Instructions:
I always prefer fresh install.
You may try, if you wish and if you already have the previous version, to flash this on top;
If you are doing fresh install, see original instructions (full wipe).
P.S. When you boot for the first time, you will get:
1. Notificaiton that email app stopped (disregard it, the app will work without any further messages)
2. Notification that SU binary should be updated: follow instructions
Regarding bootloops: Do a fresh install, which is always preferred. Also, remember, custom roms based on Cyanogen want all system apps signed by the same key. If you have SU or any other app that you installed in the system (and then flash update on top) that means that those apps are signed by different keys, which would result in a bootloop during subsequent updates. Do research and learn about not messing with system apps. Neither SU nor any other app needs to be installed in system. Also, the same applies if you decompile and mess with a system app - once you re-compile the app, you'll have to sign it and your key is different, which again means bootloop.
Also remember that this rom is designed to work with Stock JB 4.1.2 kernel only. If you have an unlocked bootloader and custom kernel, you will get bootloop and/or other issues
Before posting this update, I reformatted my phone and did a fresh install: no issues. You know what it means: I don't want to hear about bootloops.
____________________________________________________________________________
Rom checked on my device: boots 100% in about 25 seconds. Just re-uploaded. This might have been an issue of a corrupt upload.
Slimbean latest release built from sources on September 6, 2014. This is for IONs with locked bootloaders. This is not Kitkat, it is based on JB 4.1.2, which is ages more stable.
Changes:
1. Open source Launcher Advanced (one of few open launchers)
2. Terminal and FM radio added (were missing in original release by Olivier)
3. Battery/Wifi fixes incorporated in code prior to building
4. Radio menu fixed (now when you dial *#*#4636#*#* and go to phone, you no longer get F/C)
5. Default network changed to LTE
The phone seems snappier than with the original release, perhaps because the rom was built on Gentoo, which is the best Linux around. But maybe it is just placebo. You decide.
INSTALL INSTRUCTIONS:
1. Be rooted, have Recovery and JB 4.1.2 kernel
2. Enter recovery, wipe System/Data/Cache (remember factory reset is not enough)
3. Flash the rom, reboot and let it settle, which shouldn't take long
4. Enjoy and press thank you or perhaps donate...
CREDIT: Olivier for initial Manifest and Letama/Olivier/MrGezz for locked bootloader patch
XDA:DevDB Information
Slimbean for Locked Bootloaders, ROM for the AT&T Sony Xperia ion
Contributors
optimumpro
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock Kernel JB 4.1.2
Based On: AOSP Slimbean built from source
Version Information
Status: Stable
Stable Release Date: 2014-09-06
Created 2014-09-07
Last Updated 2014-09-11

Pictures

Thanks for the rom. I just flashed it and rebooted.. the screen is stuck on the slimbean logo for over 10 minutes.. the slimbean logo is flashing normally as if its about to load. You think something went wrong and I should interrupt it?
EDIT: So i interrupted after about 12 minutes by holding power and volume up keys and entered twrp to go back to previous rom. Will try back later.

imm1304 said:
Thanks for the rom. I just flashed it and rebooted.. the screen is stuck on the slimbean logo for over 10 minutes.. the slimbean logo is flashing normally as if its about to load. You think something went wrong and I should interrupt it?
EDIT: So i interrupted after about 12 minutes by holding power and volume up keys and entered twrp to go back to previous rom. Will try back later.
Click to expand...
Click to collapse
I'll look into it. Did you do system/cache/data wipe prior to flashing?

Sorry to ask again but can we have INLINE/INVOICE CALL RECORDER like the one seen in your honami ROM. I think it was a part of 0.96w fw jellybean 4.1.2. I really need it and so do others too

optimumpro said:
I'll look into it. Did you do system/cache/data wipe prior to flashing?
Click to expand...
Click to collapse
Did anyone else get stuck on slimbean logo?

Rom re-uploaded: works fine
I checked the rom and it boots on my ION fine. Re-uploaded. This might have been an issue of a corrupt upload.

Downloading, will try tomorrow after school is out. Thank you Optimum you and your damn roms tempt me as much as i tell myself to stick to stock after CM10 had quite a few issues on my end i guess.
Also on a side note if you need mirrors, I can make two or three.

Can we have kitkat like notification quick settings in this rom ?

optimumpro said:
I'll look into it. Did you do system/cache/data wipe prior to flashing?
Click to expand...
Click to collapse
Yup, I wiped system/data/cache and haven't had any problems with flashing other roms before/after this rom.
I see that you re-uploaded.. will give it a try later today. Thank you.

I had the same problem, stuck at the logo. I'll try another download too.

tgilmore16 said:
I had the same problem, stuck at the logo. I'll try another download too.
Click to expand...
Click to collapse
The first download was corrupted and removed. The current one is good.

can someone post the screens please!!

Works Great
optimumpro said:
The first download was corrupted and removed. The current one is good.
Click to expand...
Click to collapse
It's working great now. I installed an Xperia z2 ported launcher and the two together are running fine.

tgilmore16 said:
It's working great now. I installed an Xperia z2 ported launcher and the two together are running fine.
Click to expand...
Click to collapse
What about camera? Have you found a better camera for this rom?

Camera
imm1304 said:
What about camera? Have you found a better camera for this rom?
Click to expand...
Click to collapse
I'm not really a picture taker. Post #3 in this thread has a flashable camera. I'm not sure it would work on this rom, but I would flash it and if it didn't work just do a restore from backup.
http://forum.xda-developers.com/showthread.php?t=2480608

Small Apps
Does anyone low of how I can get small apps back? Although they're not a deal breaker, I actually used a couple of them and would like them back.

tgilmore16 said:
Does anyone low of how I can get small apps back? Although they're not a deal breaker, I actually used a couple of them and would like them back.
Click to expand...
Click to collapse
You can try these:
http://forum.xda-developers.com/showthread.php?t=2066827
But that would go against AOSP nature of this rom.

tgilmore16 said:
I'm not really a picture taker. Post #3 in this thread has a flashable camera. I'm not sure it would work on this rom, but I would flash it and if it didn't work just do a restore from backup.
http://forum.xda-developers.com/showthread.php?t=2480608
Click to expand...
Click to collapse
Thanks, but that camera doesnt work on this rom.. because it needs the honami framework.

Honami Sense AOSP
imm1304 said:
Thanks, but that camera doesnt work on this rom.. because it needs the honami framework.
Click to expand...
Click to collapse
Ok, I'm slowly catching on. I switched from iPhone a couple of months ago and had gotten an HTC One which I unlocked the boot loader, did the S-Off and rooted. I run AOKP on that phone and the xperia was a backup to carry when I'm running or cycling. As it turns out, my wife's iPhone is messing up so I've put a sense rom back on the One. She likes getting that feed screen and all. Now the Xperia is my main phone. I guess Honami is the Sony equivalent of proprietary like sense is to HTC.
I've found I like the Sony's and will probably replace the HTC with a Z1 or Z1 compact but I need to do some research as unlocking the boot loader is a requirement. It wasn't so important on the ion due to its purpose, plus I couldn't find an I or H at a reasonable price.
I realize I've gotten wordy and a touch off topic and apologize.
I'll keep my eyes out for a camera and as for the multi tasking, I forgot there's an xposed app that may allow some multi tasking.
I really do appreciate the ROM and am especially grateful to the dev of this rom for making it usable on a locked boot loader.

x9076 with R63419 LCD working recoveries

TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...

tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?

GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/

tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two

I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).

GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.

I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!

sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).

So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.

Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!

Does the offical TWRP and CM support this find7 with new LCD????

Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.

Double the question. Lack of working TWRP is just fatal to any tinkering.

GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit

Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!

Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks

betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!

djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.

betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....

Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1