Develop Bugs

[4.4] CyanogenMod 11 nightlies

They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.

Flash with stock recovery?
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx

dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
You will not be able to flash this with the stock recovery. I imagine once it goes stable CM will push out an official update that will work on the stock recovery setup.
Until then, TWRP works great: http://forum.xda-developers.com/showthread.php?t=2537080

dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.

Harfainx said:
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Click to expand...
Click to collapse
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.

mcteague said:
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
Click to expand...
Click to collapse
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk

Harfainx said:
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.

Entropy512 said:
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Click to expand...
Click to collapse
Correct. Currently since they're coming direct from CM as nightlies, they aren't final stable versions. Those will be released like the other two were, and I'm sure will be built to flash in the N1 Stock Recovery.

Location not working
location still not working on latest nightly (130214).
anyone has any idea on how to fix it? the 240114 nightly is not longer on the getCM servers.

Anyone on M6? Thoughts?
I went straight from CM10.2 (CM edition N1) to 11 M6, so I don't know how battery life compares with Omni or other ROMs... would love to hear from those of you that have tried other ROMs and can compare with M6.
With M6, I am getting ~4% battery drain over 7 hours overnight (2G network on only).

All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Hi,
I am trying to install Cyanogend mod. N1 a OPPO
The steps are simple, but not working,
I've tried: (http://download.cyanogenmod.com/?device=n1&type=snapshot)
** Cm-11-20140804-SNAPSHOT-M9-n1
cm-11-20140805-NIGHTLY-N1
cm-11-20140124-EXPERIMENTAL-n1.zip
They all show the same error.
"Installation failed"
I downloaded the. zip for wifi, ethernet MAC, WINDOWS ........ and still shows the same error.
:crying:

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Sorry to bump a 3 year old thread for such an unrelated reason, but you have PMs disabled, and, well, CM11 is not that appealing anymore so I'm confident not many people are gonna read this anyway [any mods reading this, please spare my soul :silly: ]
That said, I just wanted to ask you why you rated my porting of LAOS 15 Trebuchet so poorly, since you didn't leave any comment; if it's some bug, crash or other error i can look into it.
BTW you can answer me on the app's thread if you wish (https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436)

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Thank you for leaving your feedback, here are some answers to your points:
- (update mechanism) i actually caught a nasty bug in XDA Labs web console which prevents me from uploading new builds there (and I also deleted all previous reviews in the attempt to reupload the app ??); (i already filed a bug report and managed to get the dev's attention so I hope it gets fixed soon)
- (open source) being a porting, the app mostly shares the original staging/trebuchet15.1 source code, with only a handful edits for fixing crashes due to compatibility errors (and is built with gradle plugin 2.3.3 instead of 3.0.1)
- (very buggy) it inherits all current staging/trebuchet15.1 bugs, not that much from my tests, but yes, there are some

Wifi Region code Connectivity problems: A Solution

Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk

arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later

atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.

arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.

atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.

arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.

atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of

arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess

atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL

arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone

atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.

Flashable zip added for new Commotio Rom Nightlies

Any chance to apply the patch to a stock rooted rom?
Thanks

Region Code
Hi can someone fix this file for region code?

nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.

Can someone post the patch for latest cm nightlies?

nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based

nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.

[Q] Very low screen bright after reboot

Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot

reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411

muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again

Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help

reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment

You must install the UKM scripts from recovery. Read the op from the red kernel thread...

edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...

muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium

ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.

muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium

ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.

muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium

ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055

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

Any idea to port 5.0.2 from SM-P900 to SM-P600?

OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?

That would be great and highly appreciated. :good:

kornelius1982 said:
That would be great and highly appreciated. :good:
Click to expand...
Click to collapse
start from
http://forum.xda-developers.com/sit...pub-2900107662879704:4763122713&ie=ISO-8859-1
ask help from sktjdgns1189 and arter97

enotar said:
OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?
Click to expand...
Click to collapse
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."

Compile a kernel almost all the effort (95)% to port a room.
Here´s the first thing we need to do.
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
I´m downloading kernel source of sm-p901.
Here is the index sm-p900´s kernel sources:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-P90
wulkanat said:
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."
Click to expand...
Click to collapse

Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk

If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device

enotar said:
Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
would be better to use the T900 Version with a existing Kernel (don't know if it works ). Just to have it more simple. If it does not work... we can use the P900 Version
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
Wbdsgnr said:
If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device
Click to expand...
Click to collapse
good idea, I will try to boot with T900 Kernel first (Firmware is downloading right now ), but I will also give the P900 Kernel a try, if the T900 Kernel does not work
Found this in a ROM in SM-P900 Forum:
"If you are on KitKat•Make a EFS backup
•Make a Nandroidbackup.
•Download rom and place on your ExternalSD.
•Flash the Lollipop bootloader before installing the rom ar it won't boot.
Here you find the Lollipop Bootloader and Odin package that you need to install it on your device when in download mode.
If you want to revert back to KitKat rom you need to install the kitkat bootloader! You find it here and you flash it with Odin.
•Full wipe is needed and now you can install the rom."
Maby the Bootloader is the Reason why it does not boot?

I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.

enotar said:
I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
already tried it out with a Tab S ROM . And for now, (~10 sec left) i'm on KitKat back.
Did not work. But it was a try... so, black screen, and reboot. Kernel or bootloader? It does not Boot with ValexKernel too, but this is a AOSP kernel. (and yes, I'm back on Kitkat)

Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk

enotar said:
Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I have already a Ubuntu iso, so I will try to install it in VMware Which Kernel? from P900 or T900? I will try the P900, if there is no a reason why not.

I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.

P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk

enotar said:
P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Nice!

Wbdsgnr said:
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.
Click to expand...
Click to collapse
The one who made the TW 5.0.2 ROM for SM-P605 just get it too...

I'm hoping the same that someone will port p900 to p600 as both are 99% identical. @enotar, I think T900 not a Note series Tab and doesn't have S-pen functionality. So, you might wanna try P900 rom.

T900 not a Note series !!!! doesn't have S-pen functionality

alex22280 said:
T900 not a Note series !!!! doesn't have S-pen functionality
Click to expand...
Click to collapse
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk

enotar said:
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
ask for help from sktjdgns1189 ,Alan-B and arter97 (I am use a port 5.0.2 for my P605 from Alan - B)
for kernel ....arter97