Develop Bugs

[ROM][4.2.2]CyanogenMod 10.1 Nightly builds

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CyanogenMod 10.1
Sauce: https://github.com/CyanogenMod
Downloads
ROM: http://goo.im/devs/cdesai/cm/
Google Apps: 1 2
Installation
Note: this ROM uses the same partition layout as recent CM10 builds.
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Known Issues
Bootanimation looks weird for the first few seconds.
Change Log
20121206
Initial release
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Use these commands to get a logcat and dmesg
Code:
adb root
adb logcat > logcat.txt (wait for a few seconds then press Ctrl + C)
adb shell dmesg > dmesg.txt
Credits
humberos, sbradymobile, jt1134, pawitp and everyone else involved in coding and debugging.

EDIT: Builds for all 4 variants up.

Manly tears, My Tab is ALIVE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

huge thanks to all the developers working on this.
Photosphere works?

Will be testing this out right now on mine Thanks for all the hard work!

12-6 11:52 AM CST: Thanks! Downloading now!
12-6 1:10 PM CST: Attached 1st+2nd run FULL+Warning+Error filtered versions. (no crash's or issues, attached for due diligence of first run browsing)
12-6 1:15 PM CST: Attached 3rd run FULL+Error filtered logcat. (no crash's or issues, attached for due diligence)
12-6 3:25 PM CST: First random reboot, had logcat attached the entire time, didnt catch anything, attempting to get dmsg
12-6 3:35 PM CST: dmesg attached, but dont know if it will be helpful*...
12-6 4:15 PM CST: another dmesg after crash, was just hitting the back button out of YouTube...
12-7 11:15 AM CST: Added note about rotation issue
12-12 2:10 AM CST: Added logcat/dmesg's in relation to the Google Now/Sound Recorder**
BACON!
So far:
Not working:
-Bluetooth | Known 12-6-2012
-Automatic Backlight | Known since CM9
-Torch aka flashlight | Works, Extreme enable delay, 3-10 sec
-Camera/Video | Auto Flash broken, no resolution/advanced options
-Manual Rotation/Orientation reverse | landscape rotation is reversed/wrong, 270 instead of 90
Working:
+Auto Rotation | another poster said it didn't work, but it works for me
+Clock | another poster said it didnt work, but it works for me
+Market+Google Stuff | download and install of an App was successful + run
+Camera/Video | Front+Back regular pictures + manual flash
Notes:
~Boot Animation is Landscape only | Known 12-6-2012
~Everything I was able to test in 20min aside from the above, worked fine
~Its been a minor irritant since CM9, but the Galaxy Tab settings always has TV out as PAL***
~While I do not have service currently, It does show signal strength, and does show carrier info
*first post should be updated to note if doing the dmesg command on the device it should be dmesg > sdcard/dmesg.txt
**It doesnt always happen using Sound Recorder, but so far, each time I have launched Google Search (aka Google Now) moments after launch when it seems like its initiating, it locks up the tablet, there was one time I was able to use it, but I havent been able to replicate that good luck all day/night last night attached is the error's from logcat (I didnt see anything) and the 3 dmesg's I tried to capture after the device rebooted from the crash/shutdown
***I have the P1C or the CDMA variant, the Verizon Galaxy Tab, AFAIK, its a US device, always NTSC never PAL, am curious to know if the default can be changed PER device/model, if not, I understand seeing as the forums at least seem to be devoid of many other CDMA users vs GSM users.

So far
WORKING:
-WiFi: WPA2 seems to be not supported or my channel has been setted up wrong! (i cant contect to my wlan )
-Auto Rotation
-GPS
-Mobile Data (RIL)
-Display Rendering
-3D (played GTA III on it, works very well)
-Clock works fine
-Camera (no flashlight -.-)
-Gollum
-Clock works
Thats all so far
Some Screenies

Hammerfest said:
lack of normal advanced options
Click to expand...
Click to collapse
On devices running Android 4.2, developer options are hidden by default, helping to create a better experience for users. You can reveal the developer options at any time by tapping 7 times on Settings > About phone > Build number on any compatible Android device.

sbradymobile said:
On devices running Android 4.2, developer options are hidden by default, helping to create a better experience for users. You can reveal the developer options at any time by tapping 7 times on Settings > About phone > Build number on any compatible Android device.
Click to expand...
Click to collapse
Thanks...
also, never thought id have a split feeling about something, but as much as i personally hate this change, its... interesting!
changes made, going to play with it for a bit, will update my post again if need arises
EDIT: where can I disable lock screen rotation? lots of changes from 4.1 /~

Awesome!! Thanks to the devs for keeping are tabs alive ! Will test it :good:

about to download CM10.1 now, Ive been patiently waiting for 4.2 for a few weeks now, BIG UP to C.M TEAM & all DEVS that made this possible for our BELOVED P1000. Nuff RESPECT...!!!!!!!

[email protected] said:
about to download CM10.1 now, Ive been patiently waiting for 4.2 for a few weeks now, BIG UP to C.M TEAM & all DEVS that made this possible for our BELOVED P1000. Nuff RESPECT...!!!!!!!
Click to expand...
Click to collapse
I downloaded the rom and gapps about an hour and a half already and must say it responds great and its quick with no lags at all, however i cant figure out where to find the connection to tap when I plug my USB into the computer, usually a notification pops up up top and I would then pull down the notification page but its not being recognized when i connect, and ideas why, i re wiped and flashed cause i had a lil problem with the google page being upside down but that got fixed when I re flashed my device. any help will be appreciated, and thanks again to every involved with the rom for keeping the hope alive...

How can I change landscape to portrait layout?

maihuuquan said:
How can I change landscape to portrait layout?
Click to expand...
Click to collapse
I have not found rotation controls anywhere I looked, only Auto rotate and locked (toggle)... HOWEVER, that doesn't meant they aren't there, it also doesn't mean they are... I didnt know the new trick to get the Developer/Performance options in settings, so I will wait for the official word!
Speaking of rotation, with CM10.1, it seems that the rotation option in many programs flips portrait in the reverse direction! In CM10 (last I used was CM10 nightly 12-2-2012, and its a default setting I change upon each fresh wipe), when I set my launcher to portrait only, it was fine and the portrait direction was level to where my home/back/search/menu buttons where on the right, which is right as it should be (har har?), now when I set the option for Portrait mode in my launcher its flipped upside down with my controls on the left hand side (might be good for the lefty's)!
Ill add that to my earlier post as well, but Ill do it in the morning when I lookup what the orientation degrees are so as not to make an even further fool out of myself!

okay, so anyone know how to open recent apps? because i tried to press home button, but it doesn't show anything expect my tab keep buzzing.
thanks!

Some applications turn bottoms up after starting.

Great great job!!!!
I'm now downloading it. You guys really ROCK! You are keeping P1000 so alive.
---------- Post added at 03:49 PM ---------- Previous post was at 02:56 PM ----------
So thankful to CDESAI. However, hopefully in the next build or so we can now enable soft buttons navbar.

Nice ROM!!
Cdesai,
The ROM is excellent for a experimental release..
There are just small adjust to do...
List of Bugs:
- Bluetooth, as you informed before.
- Panorama photo show revert (mirror) image.
- I didn't found the Recent apps buttons option.
- Rotation option in many programs flips portrait in the reverse direction (as informed for @Hammerfest)
- Here doesn't mount USB automatic (i use a app and its works, normally)
- I cannot set a grid apps correctly.
All the rest works fine!!
It is very smooth..
Congratulations for all devs.:good:

any one can give me screenshot please...?
:fingers-crossed::fingers-crossed:

rheen said:
any one can give me screenshot please...?
:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Screenshot for this build? I think nothing visually change. Mostly are the same. Except the status bar pull down and the toogles.

GNex JB4.3 touch response time experiment : 85ms

0. I'm new user. I cannot make any links. remove replace ^ to .
1. Short english.
I'm not native English speaker. My grammar is bad.
2. Sweeter jellybean 4.3! Faster, Smoother, More Responsive.
: According to Android developer page, touch latency has been improved on Android 4.3.
3. TouchMarks - Test about <= 4.2.2 Devices.
: GSG4, HTC One, MotoX. they're all <= 4.2.2
4. So I built my own touchmark device.
Sensor/device :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CdS Sensor/ and resistor for voltage dividing.
Button / pull-up resistor.
I have only one phone/camera, so my whiteboard eraser will show how the experiment environment is set.
As you know, the plastic button cannot make a touch input, so I attached some conductive film which will make a touch input when the button contact on the screen surface. I taped screen around to minimize false inputs.
Android App, Arduino code :
github dot com /foriequal0/TouchTest
5. Experiment.
a button contact on the surface -> arduino will record the timestamp
-> touch event will arise -> screen will brighten
-> CdS sensor's resistance will change -> Arduino will record the timestamp, and send latency time to the computer.
Button's stroke is very short (<1mm) and I touched screen very fast so, time difference between button click and touch input can be neglected.
I've tested on these devices
GNex : JB4.3, Rooted, recent Fancy kernel, zRam enabled, Governor OndemandPlus(governor change won't made big difference)
SGS2 : JB4.1.2(Korean, SKT), My friends' own. no rooted, many apps installed.
SGS2 : Gingerbread(I forgot the build number. Korean. SKT), Factory resetted.
Optimus G Pro : JB 4.1.2(Korean, LG U+), My colleague's.
6. Result.
GNex
x axis : sorted sample.
y axis : response time(us)
left tail and right tail may be false input/lag caused by background apps.
uniform distribution between [75ms, 92ms]. note that interval of 1 frame on 60FPS is 16.6ms
SGS2(JB):
uniform between [115ms, 150ms]. I think there might be some synchronization failure. touch response distributed on 2 frames.
SGS2(Gingerbread):
uniform between [100ms, 120ms], but have smoother tails than SGS2's
OptimusG Pro:
Fairly better than samsung's. I don't know why.
Have anyone a question/improvement/objection?

Nexus 5 response time
Hi there, great experiment, seems like android response time isn't so bad after 4.2
Just wondering, would you be able to get your hands on a new Nexus 5 and do the same test? apparently it has good touch screen which should result in a low response time.
Or someone could also do a complete Touch+Audio latency test. This is the way I like to do it:
Install a musical app, either drumming or keyboard.
Install a sound recording app,
Start recording audio and give the screen a good tap in the musical app, this way both the "tap" and resulting drum or keyboard sound will get recorded.
Open that saved .wav up in audacity then zoom in and observe the visual audio waveforms then measure the distance between the TAP and the sound actually playing.
On my devices I was getting around 175ms if the particular music app used the "Sound Pool" class or 250+ if using "Audio Track" I'm running android 4.2.
I hope you or some lucky dude with a Nexus 5 can do this test, there are dozens of nexus 5 reviews popping up online but NONE provide this sort of information, and if anyone wants the Nexus 5 for real-time music creation we need to know this info, and we need to make it public
**I know the test isn't accurate down to the ms but it is accurate to around 5-10ms which should be good enough to gauge its approximate performance.

Hi! and thank you for your reply!
ianmere said:
Hi there, great experiment, seems like android response time isn't so bad after 4.2
Just wondering, would you be able to get your hands on a new Nexus 5 and do the same test? apparently it has good touch screen which should result in a low response time.
Or someone could also do a complete Touch+Audio latency test. This is the way I like to do it:
Install a musical app, either drumming or keyboard.
Install a sound recording app,
Start recording audio and give the screen a good tap in the musical app, this way both the "tap" and resulting drum or keyboard sound will get recorded.
Open that saved .wav up in audacity then zoom in and observe the visual audio waveforms then measure the distance between the TAP and the sound actually playing.
On my devices I was getting around 175ms if the particular music app used the "Sound Pool" class or 250+ if using "Audio Track" I'm running android 4.2.
I hope you or some lucky dude with a Nexus 5 can do this test, there are dozens of nexus 5 reviews popping up online but NONE provide this sort of information, and if anyone wants the Nexus 5 for real-time music creation we need to know this info, and we need to make it public
**I know the test isn't accurate down to the ms but it is accurate to around 5-10ms which should be good enough to gauge its approximate performance.
Click to expand...
Click to collapse
Hi! and thank you for your reply!
I checked this thread for a long time. sorry for the late.
I highly inspired by your audio latency experiment!
I lately bought a new nexus5 and now I'm full with willingness to build new experiment on it, but unluckily I'm very busy day and night. I have to be stucked in my office for a while
Whenever I get some new results, I'll promise not to hesitate to post it on this thread.
Thank you.

Trying to replicate your experiment
Hello foriequal0,
I have tried to replicate your experiment with little success.
Here are some pics of my setup (Arduino Uno)
Note the conducting film around the switch (not easy to see) to make contact with my finger
and some results...
Not sure what might be the conclusion (especially for trial 3 - D2-727 tablet).
I am concerned whit the high variability of my results ...
This is my first post on a forum so please indulge if it is not perfect!
2014 May 1st addition:
After many tests, I achieved more stability and here is the result for the D2-227 Android tablet:

[App] Kickstarter Browser

Hello fellow windows developer.
I guess I'm not a frequent poster but I need your help!
I need your feedback on my latest Windows 8 app: Kickstarter Browser. The thing is, I just got it release just to have a initial release but I need feedback on it. It's easy to feel satisfied with your app because you are familiar with it. I do have a general idea where I want to go with the app (adding twitter share, add favorites) but as far as GUI I'm not really sure. So any critic is welcome to just post here, perhaps even screenshots if there is anything specific you want to point out. If you have good things to say you can also review it windows 8 store. (Please do not post reviews/low stars saying it's bad, remember this is just my first release and I will improve it over the coming months using your feedback and then you can give a proper review ) If you give me feedback which I'll use to improve the app I will, if you want, add you to a thank you list in the App description.
As far as adding, login/pledging from the apps etc. there are no official Kickstarter API and the API I'm using is Very restricted.
Anyway, please give me feedback and I will be very thankful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hmm, well I tried to install your app but the MS store is insisting that I am not connected to the internet, it worked fine 2 days ago on the same connection and I am clearly on the internet right now. I'll have to takes its suggestion of trying again later.
Picture looks alright but I cant see myself using the app if I'm honest, I just dont browse kickstarter. If I can get it to download I will pop back with something more useful to you

SixSixSevenSeven said:
hmm, well I tried to install your app but the MS store is insisting that I am not connected to the internet, it worked fine 2 days ago on the same connection and I am clearly on the internet right now. I'll have to takes its suggestion of trying again later.
Picture looks alright but I cant see myself using the app if I'm honest, I just dont browse kickstarter. If I can get it to download I will pop back with something more useful to you
Click to expand...
Click to collapse
Thank you for trying and thank you for giving me you 2 cents on the screenshot, hopefully you will be able to download it soon. I am at hard work to bring another release of this app within two-three weeks, but I do hope some more people would give me their opinions.

Update
I've made an update for this app. Though I have not received a single piece of feedback.
This time I bring the ability to see videos in the app and to search through descriptions of projects to find specific words (This is something the normal kickstarter.com website cannot do). I also updated to GUI to look much better and fixed bugs, you can find the app update here:
Please download, try it and give me some feedback.
Thanks.

Nice! Just gonna give some friendly feedback here: first, it would be nice to have the spotlight words in the top-left clickable, so I could select technology or whatever. Second, the tiles for each result could use a little more modern. By this I mean separate each tile a little, get rid of the rounded effect, and maybe make the background for each tile the project picture. Other than that, maybe some more background colors on the app would help. But really, nice work!

Thanks
C-Lang said:
Nice! Just gonna give some friendly feedback here: first, it would be nice to have the spotlight words in the top-left clickable, so I could select technology or whatever. Second, the tiles for each result could use a little more modern. By this I mean separate each tile a little, get rid of the rounded effect, and maybe make the background for each tile the project picture. Other than that, maybe some more background colors on the app would help. But really, nice work!
Click to expand...
Click to collapse
Wow, thank you. It was very observant of you to notice the kind of "Rounded effect". I have taken your advises into consideration for my next release. I will be releasing a Halloween update within the next few days and will post here when it is certified and live. Thank you SO MUCH. You are the first to give me some suggestions, and I've asked for help on quite a few forums.
The next update will have many new features I hope you all will enjoy.

Update!
Well, you could say I really buckled up last night and started my code, because here is the halloween update!
I focused on customization and user experience this time. The change log follows:
-Changes in version 1.2.0-
Big GUI update
Multitask support added (view video while using other apps)
Added tool tips
Added FAQ to project description
Significantly improved search times when searching through descriptions (by 20 percent)
Search now list projects as they are found (not when search is done)
Added settings for spotlight
- It's now possible to add/remove and enable/disable individual spotlight categories (found under settings)
Added the possibility to to favorite projects
Added favorite page (accessed by swiping down from top or right click the top of the screen)
Removed crash bug when no internet connection
Anyway I hope you all will download it and try it (and tell me what you think). I will be taking a one week break from coding Kickstarter Browser to recharge my batteries and get inspired to do some more work.

Update
I hate how it feels like I'm spamming/bumping my own thread but I just want to keep you guys updated and hopefully get more feedback from you guys!
So I've just got the post-Halloween update certified. Change log:
Revamped start screen
Added playback controls (Play, stop, mute, video time bar)
Added video full screen playback
Added sorting projects in search
Added backgrounds
Added browsing categories in search screen/start screen
Squashed bugs
So this is the first update based on feedback from users and feedback I've asked for from various forums. One point of feedback was really important. The user felt that when you first start the app you are welcomed with a screen with a huge gap in the middle. So I made the middle part dedicated for browsing through categories and all the searching should be done through the search screen. Another user told me that the app doesn't bring anything new to the table in terms of searching and finding, so I added more search options. The third big feedback I got was that the app was boring, colorless and not nice to look at, so I reworked the layouts and made it possible for the user to change background color/add background image. The last feedback I did take into consideration for this update was that the search screen was a bit confusing and that the video playback lacked features, so I rearranged the search screen a bit and added video playback features (it now has play, stop, mute, full screen and a timeline)
So you see, I use the feedback I get to make the app better, please keep it coming and I will possibly implement it.
Thanks

Live tile update
I guess you all know what this post mean by now.
I've just release update 1.2.5. Inspired by another app this update brings the ability to create live tiles of projects to have them on the system's start menu screen and keep track of projects. Change log:
Added more backgrounds
Added ability to create live tiles of projects
Added all subcategories to browsing
Refined browsing
Fixed bugs
Added Help/FAQ to top appbar
Moved settings to top appbar
Thanks

This is the last update this year. Well, it's a few updates since I last posted but I thought I might as well post now
-Changes in version 1.2.7-
Revamped most pages for a more unified look
Fixed FAQ/Description load bug due to changes of kickstarter.com
Removed "find atleast xx projects" slider
-Changes in version 1.2.6-
Separated browse and search, added browse screen
Made search faster
Fixed bug where background color wouldn't load
Many minor bug fixes and clean up code

[4.4.x]Omni Nightlies for Find 7a/7s

DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!
"Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.​
This is the thread for Omni nightlies for the Oppo Find 7a and 7s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://dl.omnirom.org/find7/
Also, the nightlies support LVM for partition remapping, which allows the two internal data partitions (/sdcard and /data) to be merged into one that uses emulated storage for /sdcard (Android's standard method for ICS and later). Details can be found at http://forum.xda-developers.com/showpost.php?p=55081626&postcount=546 . LVM is significantly safer than other partition remapping solutions as it does not actually alter the underlying partition table. As a result, switching layouts is MUCH faster than methods which remap the partition table, and switching layouts is more reliable and doesn't fail in strange and difficult-to-repair ways (such as the frequent failures of another solution that can be seen in the ColorOS 2.0.2i beta thread). There's a good chance Oppo will be switching over to this method with a future ColorOS release, especially after their experiences with 2.0.2
For historical reference, I will leave the pre-nightly test builds in the Downloads section of this thread. However, these are now obsolete.
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
(this isn't a nexus, use the modular releases, not full)
Omni only supports TWRP recovery, use any alternate recovery at your own risk. Official TWRP for this device is:
http://forum.xda-developers.com/showthread.php?t=2717916
Anyone flashing this should know the usual installation drill... Flash in recovery, flash gapps, wipe data/factory reset. If you don't know how to do these things, this package is not yet ready for users like you.
Thanks go to the following people for their help during bringup:
Jake Whatley and Kristof Petho (Omni)
Max Weninger for polishing the device up and getting it up to nightly readiness after I kind of burned out
Andre Saddler and Hieu Nguyen of the Paranoid Android team
XDA:DevDB Information
Omni for Find 7a/7s, ROM for the Oppo Find 7
Contributors
Entropy512, maxwen, xplodwild, jerdog, jakew02
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2014-05-21
Last Updated 2014-09-02

Reserved
Kernel source:
https://github.com/omnirom/android_kernel_oppo_msm8974/ plus the following Gerrit items:
https://gerrit.omnirom.org/#/c/7373/
https://gerrit.omnirom.org/#/c/7374/
https://gerrit.omnirom.org/#/c/7423/
https://gerrit.omnirom.org/#/c/7651/
https://gerrit.omnirom.org/#/c/7649/
https://gerrit.omnirom.org/#/c/7650/
https://gerrit.omnirom.org/#/c/7648/
Device tree:
https://github.com/omnirom/android_device_oppo_find7a/ plus:
https://gerrit.omnirom.org/#/c/7336/
https://gerrit.omnirom.org/#/c/7645/
https://gerrit.omnirom.org/#/c/7434/
Other Gerrit items:
https://gerrit.omnirom.org/#/c/7652/
https://gerrit.omnirom.org/#/c/7460/
https://gerrit.omnirom.org/#/c/7465/
https://gerrit.omnirom.org/#/c/7103/
Also there are misc patches to increase debug logging in a number of places (the basic setting NDEBUG to 0)
Blobs: donkeycoyote

Reserved
Current status as of 05/20/2014:
GPS works
Wifi works
Cellular radio works (data and voice calls)
Basic camera/camcorder functions work
Bluetooth works (tested with Google Glass and an OBDKey)
Sensors work (except for Google Camera Photosphere - see below)
Audio is flaky - Mic does not work in speakerphone calls (earpiece only) and headsets with microphones cause the audio HAL to barf. There are probably a number of other use cases where audio doesn't work well. Confirmed working are Google Play Music, Google Maps, earpiece calls, Bluetooth calls via Google Glass (Mic in speakerphone/headphones may be fixed in the 5/30 build - won't test until tomorrow.)
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Screen-off gestures for music
"Hey, Snapdragon" voice wakeup - gotta talk to xplodwild about this
Superzoom mode (I'm about halfway there, it's in the 5/30 build but crashes when you take a shot, so effectively isn't really there...)
Known issues:
Rare spontaneous reboots due to the WCNSS firmware crashing (1-2 times/week for me)
Magnetometer (compass) gets "Stuck" if you use Google Camera
LPM (charging when device is off) is broken - device may charge but screen gets stuck on at the Oppo logo. (may sometimes happen when rebooting on charger)

Woot!

Here we go!
Sent from my OnePlus 7a

Finally a good vanilla build
My camera lenses produce a clicking noise everytime a camera app is closed. It didn't happen with color OS before. ¿is there any issue with it?

If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !

Does VOCC Charging works now?

Also, 3-ring headsets do not work (ie like the headset that came in the box).

Great work guys... Running super for an alpha.

There's a typo, it's build in may, not april :good:

lesscro said:
If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !
Click to expand...
Click to collapse
I'm not a big fan of flashy posts with lots of graphics. Means more data for my browser to load.
hulicow said:
Does VOCC Charging works now?
Click to expand...
Click to collapse
It's in-kernel, it's pretty much impossible to get a device with working charging without VOOC.
kristofpetho said:
Also, 3-ring headsets do not work (ie like the headset that came in the box).
Click to expand...
Click to collapse
That's what I meant by headsets with mics barf. (although headsets with media controls might be in the same boat...)
xabierd said:
There's a typo, it's build in may, not april :good:
Click to expand...
Click to collapse
WHAT? It's not 4/20???

No problem... then trash it as i say...
cheers

It's begun. Glad to see you got it through entropy.
Once the initial hiccups are ironed out this phone can finally take it's place as the stylish and capable smartphone it should have had from the very start.
Gesendet von meinem One mit Tapatalk

Fix for 3-ring jack not working incoming.

Entropy512 said:
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Doubletap to wake
Screen-off gestures
Click to expand...
Click to collapse
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them

maxwen said:
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them
Click to expand...
Click to collapse
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.

Entropy512 said:
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.
Click to expand...
Click to collapse
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1

maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
Wasn't that a different patch?
I'm seeing a problem where the device gets stuck wakelocked processing lots of input event spam from somewhere, or it's not properly flushing the key event queue. It's intermittent - sometimes it's absolutely fine, other times it just goes nuts.

maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
ah - no
LOL I was to much ahead and imagined another change you might
also find at some point
This one is actually obsolete AFAIKS since there is a check
for is_tp_suspended on top of the function. Think this is a "leftover"
for our properitary S2W impl that has been obsoleted

Question Change screen resolution

Anyone knows if is possible change resolution in adb? Or someting

Pretty sure you used to be able to use the following command
For resolution:
adb shell wm size 1080x1920
For screen density:
adb shell wm density 390
Obviously adjust numbers to suit your needs.
I accept no responsibility for any issues which may occur if you use these commands
Edit:
Did a quick bit of googling and found this which echos the above:
https://www.reddit.com/r/pokemongodev/comments/6554k1/_/dgfpesr

I know this is quite an old post, but couldn't find a newer one mentioning if changing screen res works. Did these commands worked fine with the 6 pro? And is there any noticable difference in battery life/performance if it does work?

I'm interested too. Give it a shot and report back on the results? I'm in the car all day, otherwise I would

There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.

B from C said:
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
Click to expand...
Click to collapse
I just tried that and needed to pull out my magnifying glass lol. Everything was so small!!

I've got mine at 474 with font set to large... happy medium for me

Gave it a try just now and it does work, however definitely not what I expected. Basically adds 2 huge top/bottomn notches and brings your rendered screen in the middle. Bottom gestures are almost impossible, as you have to start somewhere middle in the screen. And for unlocking the device - now you need 2 fingers - one to trigger the FP scanner because it ends up in the bottom right and one on the actual Scanner. Also you end up with a weirdly placed camera cutout that you cant remove.
I might try to run my phone like this for a day, as I wanted to experiment how the battery behaves. Menus seems really fast and smooth, but can be because the animations have less space and are shorter . If anyone has an idea for a command to stretch the screen over the whole display, I'd love to try.
Edit: Never mind, dumb me didnt adjust for screen ratio not being what I'm used to. After taking that into account 1080x2340 works. Fingerprint and camera cutout issues still persist though.

While this may be a little small/sharp for some people, I've been running "Smallest Width" at 720, which seems to yield a "Display Size" of 320dpi, along with default font size for awhile and have had no issues with the camera cutout or the fingerprint reader. I also use the AOD Notify app to put a glowing ring around the camera and didnt need to make any offsets so I'm pretty sure my camera cutout is where it's supposed to be.
I ran 320dpi/720width for years on a few Samsung Note devices prior to my P6P so that's what I'm used to (I'm one of those people who run a 4k tv as a monitor with no scaling). You may need to play with different dpi and font combinations until you find something you are comfortable with. In rare situations I have needed to restart the device or clear the cache for all UI elements to resize correctly after a change.

After a couple days of testing (it did indeed took me 2 days to kill my phone) I figured that for whatever reason, on the Pixel (maybe exynos) lowering the render res does indeed save some battery. On 1080p I managed to get around 1%/h - 2%/h less consumption on Screen on Time, which for people like me who manage to get 5+ hours of screen on time can result in quite of a difference. I regularly end days with something between 30-40% battery, which is still really good but I won't go to a second day as the 2 hours charge time is really annoying me .
With the lower resolution I ended the first day with 57% and I ended up with 37.5 hours of standby and 8 hours and 40 min of SoT in a full charge. I even went further by reducing the resolution to 720p, but it is really obvious that Google never made a 720p phone - almost all UI's broke and even changing the brightness was a hassle. I also believe that it might have triggered some rouge process as my phone lost 10% battery in less than an hour, so I switched back to my original 1440p.
To conclude this - is changing your resolution to 1080p worth the broken finger print - depends. In my example, I would probably do it if I know I am going on a trip where lots of pics/videos will be taken and heavy navigation use, as my phone is more of a tool in cases like that and I always try to squeeze every bit of battery I can. If google does implement the ability to change the res though - I would definitely switch.
I just wonder, why does it made such a big difference on this phone, but it didnt for S10(the only battery test I found on a video). Is Android 12 harder to drive? Or are these LTPO panels more intense on the GPU? Or is it even exynos/mali GPU not as efficient as SD on rendering UIs? If anyone wants to chime in - Id' be glad to hear some opinions. ( Or maybe I just used my phone less.. that would be the worst )
P.S. Just to say this was done on 60hz and that your milage might vary, if you decide to try. Everyone's usage is different and in my case I work from home - so WiFi connection (although router is far) but horrible signal, as I am a top flat in the UK (worst case scenario). The setting I used for the adb command is 1080x2340 and denstity was 400, although density is preference I guess and I believe wont affect battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value

liver20 said:
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
Click to expand...
Click to collapse
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel

roirraW edor ehT said:
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
Click to expand...
Click to collapse
And doesn't break the fingerprint scanner like Easy DPI changer does

There must be a way of doing it without opening the bootloader, right? Or do you guys think it's impossible without breaking stuff like the fp scanner? I'd love to lower my resolution but I really didn't want to lose all my stuff and have to reinstall everything at this moment.

Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link

B from C said:
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
Click to expand...
Click to collapse
Thanks a million for this. The module fixed my screen flickering - couldn't go over approx 50% without flicker . I set the screen brightness from within Miscellaneous. Only problem is that I can't access Miscellaneous again without module force closing (other options are fine) - looking into the reason for it.