Related
PLEASE NOTE THE FOLLOWING:
This is BETA code. Some things do not work and you should assume there will be BUGS. I am not responsible if you brick your phone with this or any other firmware. You are your own warranty once you start loading firmware. Please do NOT post about anything that's in the "broken" list; I will ignore you if you do.
If it's not listed as working or broken below then that particular feature has likely not been tested at all.
Kernel: Mine, built from Motorola's released source. Includes Smartassv2 governor and ext2, ext3 and ext4 filesystems plus MSS clamping support.
Codebase and credits: Originally sync'd from Isaac's work, heavily modified at this point. Isaac deserves the credit for getting the base code to boot and getting me interested in hacking on it.
What's working
Pretty much everything, except what's listed below.
What's known BROKEN:
Hdmi non-functional
The is an interrupt storm if you enable both Wifi and Bluetooth at the same time. Don't.
Front camera does not mirror snapshots or video, but does on preview.
Occasional force-closes when switching cameras front-to-back.
What's Intermittent: Nothing.
Included Apps:
Essentially nothing. Load GAPPS for Google apps (yes, you want them) by flashing these AFTER you flash the ROM:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip - Base Google Apps
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip - Google Talk (if you want it)
NOTE: You cannot provision on the CM7 ROM (the "Activate" apk, if you grab it from the Triumph, will not work - it appears to run, but does not function.) You must be provisioned using the stock ROM before you load this code. I am attempting to fix that, but am not confident it can be fixed as it appears to want things in the framework that I have no way to discover or duplicate.
To install:
1. MAKE A NANDROID BACKUP! I cannot emphasize this enough - and make sure you keep that backup somewhere SAFE. Most notably there is no way to activate the phone on CM7 at this time, and there may never be. If you need to change your phone number or similar you need to swap back to stock firmware. If you lose the ability to do that you will be pissed. Consider yourself warned.
2. Place the file in the below post on your SD card in the root.
3. Boot to clockwork by turning your phone off and then hold BOTH volume buttons while pressing POWER. Release power when the phone vibrates and continue to hold both volume rockers until Clockwork comes up.
4. Important: Clear the cache and data ("factory reset") If you fail to do this CM7 will blow up on boot unless you are coming from previous RECENT build. You've been warned! If you're coming from an OLD build (or stock) format /system as well.
5. Select the ZIP file from the SD card (about halfway down on the top screen of Clockwork to get to that menu, then the first entry and point at it.)
6. Commit the update.
7. If you formatted /system (and if you're coming from STOCK) flash GAPPS (below; the first is the standard GAPPS apps, the second is Google Talk) using the same procedure in #5 and #6.
On first boot it will take about 2 minutes before it comes up; if you have lots of apps it may take longer. Provided you see the little CM7 guy with the rotating arrow, it's working - be patient.
Current code download link(s)
11/19 - vB.08 http://www.mediafire.com/?bhmitbx7weqf8g2 - Wifi Tethering / FINAL
11/06 - vB.07 http://www.mediafire.com/?eqdfo7ktmtuq281 - Haptic soft keys / light sensor
10/30 - vB.06 http://www.mediafire.com/?qj28ip6o09j1ai6 - Screenshot / restore GB Launcher
10/29 - vB.05 http://www.mediafire.com/?rjf20vb74oc0irb - Cleanup release; see below
10/26: http://www.mediafire.com/download.php?wwj1l5lzjb4glfy - Wifi/PRL/Prox Sensor
10/22: http://www.mediafire.com/download.php?nssofns6sljfj33 - CIFS/Prox Sensor/USB Tether
10/16: http://www.mediafire.com/?jg5matblx1d7bq2 - First BETA
10/12: http://www.mediafire.com/download.php?wtwvx80ccsz8vfi - Last ALPHA build
Note: Loading this version requires a Clockwork that understands ext4. The following version is recommended: http://www.mediafire.com/download.php?acpcd9xtlpzqge1
Expected to be fixed in the NEXT build -
Work continues on the list in the first post along with tracking bugs that have been posted to GitHub.
Change Log (tracking as of 9/5), reverse chronological order:
11/19:
Wifi tethering is now built into the code (from Isaac's work); untested other than the fact that it does come up and is believed working. No other changes. FINAL RELEASE.
11/06:
Haptic feedback on soft keyboard now works and is treated as any other "virtual key" off the screen. Kernel modified to multiply light sensor readings by 30; this "sorta" aligns them with actual lux values (not really, but I don't have a light box that can get me a closer integration formula) and makes possible the CM7 options for "jump" settings, hysteresis and such to work as designed. No other material changes against b.06.
10/30:
Screenshot from power menu fixed and Gingerbread default launcher restored.
10/29:
Cleanup release. 2.3.7 codebase merge with CM7 upstream completed. "99memory" file added - see the notes below for how to tune this if you want to. Significant change to power management was made in the kernel; if you have Wifi turned off the phone will enter deep sleep, but if it's loaded then the sleep state is held at one level higher to prevent Wifi lockups. Note that data, when active, is a major power pig, even if nothing appears to be using it. It looks like Sprint has some "keep alive" processing going on either at the network level or in the actual CDMA driver code (which we don't have) that plays hell with power consumption. In short, with a data connection up I can't get materially under 30ma when idle and it's either the carrier or the CDMA radio code doing it - either way, I have no way to change it as there's no source to the chipset code available. Juice Defender, assuming Wifi is off, does a amazingly excellent job in conjunction with this release in shutting down the data connection and "waking it" once every 15 minutes or so to check for new notifications. It makes a huge difference in power burn with the phone in your pocket. You decide if its worth losing "instant" data notifies. I noted the same battery behavior on stock (Froyo) when I first got this phone, so my best guess is that this is in the radio firmware itself. Last alpha release pulled.
10/26:
Wifi wakelock problem is fixed. PRL now comes out of the radio and proximity sensor has more changes made. Note that the prox sensor may "flash" if you put the phone to your head before the call connects (before the "vibrate" after you dial); it should stop as soon as the phone goes into the "active" state.
10/22:
CIFS support via kernel loadable (.ko); NOT loaded by default as its very large. You can enable this in the startup scripts if you want it. USB tethering fixed. Proximity sensor "blinking" fixed. Various other minor changes as well.
10/16:
Data drop detection/correct code added. Front camera options that were unsupported in the hardware (and which could cause lockups) removed. Memory management changes made to improve performance. Soft keypad now PWM controlled (change levels under the CM7 options if you don't like my defaults) and other cleanup. Note: This release was early as there's a problem with some of the dependencies in the GIT servers, and as such I could not do a clean "verify builds from zero" run. Note that front camera mirror mode is enabled for preview but is NOT on snapshots and taken videos; this is being investigated as the mirroring should be on but doesn't work when the actual picture is taken.
10/12:
GAPPS removed from base build, front camera fixes complete, rear camera will now video record in HD. Tunneling support now internal to the kernel (no longer requires a loadable) for VPN users. Previous versions REMOVED.
10/2:
Partial front camera support is now available. The camera functions properly in video calling software such as Skype. Note that the "hacked" Froyo-capable Skype does not work properly; the one in the market, however, does. Other video calling applications may work but have not been tested. The Camera application itself will display the preview on the front camera but it is flipped 180 degrees (top to bottom), attempting to switch to video mode force-closes and a snapshot attempt hangs. Don't do that, basically. These are on the list to be fixed but progress is slow due to the very hacksterish way I had to implement the camera (no thanks to Motorola on that with no source access.) Kernel has the smartassv2 governor available for those who wish it and the build tree was synced up from CM7 to incorporate their fixes and updates.
9/25
Bluetooth tethering and MSS clamping implemented. Bluetooth tether is native; the MSS clamping, if recognized by other tethering applications (e.g. wireless tether) will also function to get rid of the need to set the client's MTU.
9/21
GPS now functional
9/10 morning:
Compass/geomagnetic sensors now working properly
Lights code now honors CM7's customization screens
9/5 morning build:
Market problems with apps not showing up repaired.
To file a BUG report
Use the Bugtracker Git at https://github.com/ikarosdev/CM7_Triumph_bug_tracker/issues?sort=created&direction=desc&state=open
Filing a new bug will require that you set up a login ID on Github if you don't have one. Please note that bugs reported in this thread (as opposed to discussion, which is always welcome) may or may not be noticed and tracked; if you care about whatever you're reporting, please use the GITHub system. Bugs filed on Github must include steps to re-create the problem if you're able to do so and if you can obtain one, a logcat or other trace is very helpful. You can also look at the above link to see what issues are open (please do not duplicate already-reported bugs, although if you have comments on them adding them is fine) as well as what has bene closed which may be of interest if you're looking for what is likely to show up in the next code turn.
Notes
Do NOT tamper with the following lines in build.prop:
ro.telephony.ril_nid=97
ro.telephony.ril_prl=1115
ro.telephony.ril_class=Triumph
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
If you do there is a high probability that the radio will break. In particular the ril_class is required to deal with the oddities in the Qualcomm radio code. If you are running a different PRL you can change the prl line but it should remain present.
If you are updating from previous releases and have problems format the /system partition before you load the update. You should not need to format the data partition ("factory reset") and reload your applications, but no promises can be made at this point in development.
Custom backlight options (Settings->Cyanogen Mod->Display->Automatic Backlight) are available; you can change the behavior of the LCD backlight, including thresholds and illumination settings, the number of steps, whether averaging is used, whether hysteresis is operational and whether the button backlight is on or off as desired. Please note that unlike many devices the sensor value returned to the code is not in "lux"; it is a raw value and tops out in full sunlight somewhere under 100, with "0" being a fairly dim (but not dark) room. The default table I have loaded has the button backlight OFF for very dim ambient conditions (I like to use the phone as an alarm clock and want the buttons off at night), ON for low-but-present ambient conditions, and then OFF again (power saving) for ambient light high enough that the backlight has no real purpose. You may change this to suit yourself and your desires; some people will want the buttons on for zero-ambient conditions.
Note: As of 9/24 this load is using the "ext4" filesystem. Alternative kernels must support both that filesystem and the options CONFIG_NETFILTER_XT_TARGET_TCPMSS and CONFIG_IP_NF_MANGLE. If they do not MSS clamping will not function. If ext4 is not supported the kernel will not boot.
3g/1x data lock
If you are in a place that often switches down to 1xRTT for data due to questionable signal levels it is possible to lock the RIL to 3g mode. Note that doing so means you either get 3g speed or nothing. You need to access the "Phone Info" menu to do this using either AnyCut (from the market) or from the "Battery Monitor" Widget (go to "Tests" in the selected screen from there.) Note, however, that doing so (1) will not survive a reboot and (2) disables SMS/MMS and inbound phone calls during the time it is active. SMS/MMS will come through if you make a phone call but the EVDO-only mode for data blocks something in the radio that is required to receive and send SMS messages and the notifications of an inbound call. Since this "mode change" is actually a request to the radio ROM (which we do not have source for) this probably can't be worked around. However, I am looking into what this mode select does in the hope of being able to detect the 1x switch (which I can easily do with the existing RIL support code) and temporarily force a 3g switchback - which may or may not be highly-disruptive to data transport (if it is it's not worth doing at all, but if not...)
Note: There is an apparent memory leak in the base CM7 code somewhere. This is the cause of sensor slowdown (e.g. rotation is not immediately recognized) as the system becomes memory-constrained and ultimately will fault and reboot. I do not have isolation of this problem as of yet and have no reasonable expectation on when or if I may; for the time being I recommend a reboot on a daily basis to avoid the worst of these effects. The impact becomes particularly-severe if you use things like CoPilot that require large working sets of RAM. My instrumentation leads me to believe the problem is not in the kernel nor in the user application side of the system, but rather is in the base CM7 load. Investigation continues.
A note on overclocked kernels:
I will not be supporting these in my builds. They work, and some people want them. Isaac has built one that can (theoretically) go to 1.9Ghz.
Here's the issue in a nutshell: It's pretty easy to exceed thermal limits in a CPU doing this, and if you do, the best thing that happens is that the device becomes unstable and reboots. The worst thing that can happen is that the internal junctions in the CPU can be damaged or even destroyed. This damage is not always immediately apparent and can in fact be cumulative.
I understand some people want to overclock, but nobody really knows where "the wall" in this regard, and if you find it you're going to be very unhappy. As such if you want to have fun of this sort you'll need to load your own overclocked kernel over what I build. I respect those who are willing to take the risk but I just don't see the potential reward as being worthwhile and I don't want to be the guy that hands you a build that smokes the CPU in your phone.
Sweet man, keep up the good work! CM7 is gonna be great on the triumph.
Market fix in the latest build - please update.
Just flashed the updated ROM and so far so good. As long as the calls come through then I can wait for a full port. Thanks for your hard work =)
And on a side note, it seems like I'm getting better reception after I flashed this. (-85dBm vs ~ -95dBm to -105dBm)
The two big problems are the GPS and MMS. The MMS is a matter of hacking and time (Virgin's MMS is... odd...), the GPS is pissing me off. Again a lack of documentation strikes; it appears there's a versioning problem with the RPC stuff and the chipset and driver in question do not expose the NMEA port (which sucks.)
Awesome work!
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
The auto-brightness code was completely re-implemented (by me); it's DIFFERENT in its behavior, but I like how it behaves.
I haven't had a back key problem with either this rom or the original....
HDMI bug report
I'm just trying to help out. HDMI out does not seem to be working just wanted to report this minor bug. Overall I'm loving this rom. Great job.
Great work Genesis!
Sent from my NookColor using xda premium
Anyone experiencing issues with data?
Seems like my data is intermittent and goes in and out randomly. I still see the 3G icon (and the signal status) but it goes white (no Google services) and I have no data access.
Yeah I've been losing data. Easiest fix is to turn on airplane mode on the off. Should come back on.
I've also noticed that email 2.3 keeps force closing. Got around this buy restoring email 2.2 with titanium backup.
stock video player bug
When playing videos with the stock video player the video comes out slightly glitchy. The same thing happens with YouTube videos.
I have not noticed the problem when watching flash videos or using arc media video player (have not had a chance to test others)
Love the ability to use the different themes with theme Chooser.
Agai appreciate all the hard work. Can't wait for a custom kernel
my review
ok i would like to start this off by saying that i love you for all the work you have done, you and Isaac. this is not asking you to fix anything this is just my first impressions after using this rom for two days.
*market: i believe this was already addressed in the original post of this rom. i updated market to the newest version and ever sense it has been force closing at random times. it still works to download things and browse but it will randomly force close.
*battery life has greatly decreased since i flashed cm7. even with juice defender pro it was still a much shorter life span.
*screen auto brightness: this has already been addressed i know but i am trying to do a very in depth review. it takes a while after i turn the screen on for it to brighten up enough to be clearly visible. another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
*head set volume dropping issue. i have addressed this in a previous thread as a fix. i was hoping this would be fixed in cm7 but it must be a deep hardware issue. what happens is, when you are listening to music through the headset port and a text comes in, the phone will ring and then the music will come back on but at a significantly lower volume. the only way i have found to bring the volume back up is to make a call and then play your music again.
*music and calling: i have noticed that if you answer a call and have music playing, when you hang up the music will stay paused. i dont know if this can be fixed but i thought i would just throw it out there.
*wifi will work untill the screen goes off. the phone will not rewake and you will have to do a batt pull.
*swype fails hard. with froyo swype worked just fine but now it has very bad lag and doesnt even register when im swyiping sometimes. this is not that big of an issue because i use swype as personal preference.
*wifi wireless teather for root users. this works now! only with google web pages -_-
*mms: wont work at all. just a heads up though you can go to message settings and switch it to split messages so you can send longer messages.
as of now this is all i have but i will update this if i come up with more. as i said before i am not trying to nag you at all i just want to get my views out there and hopefully help with feature development of cm7 for the triumph.
keep up the great work guys! i cant thank you enough.
1. Market - if you loaded over the first load, you need to format /system before you do that. You've got pieces of old things laying around.
2. Battery - it's wrong (charge state) until you fully cycle it. I'm getting battery life roughly equal to the stock load (and I am off-charge a LOT)
3. Auto-brightness - This will be adjustable in the next load - the issue is that the phone turns in with the screen in the "dimmed" state and there's a smoothing period before it reacts. You can set that with the next load to make it behave however you'd like (defaults are close to, but not identical to, how it behaves now.)
4. Headset. I think this is a hardware problem.
5. Music and calling: This is a common issue with Android; when the output and input sources get reassigned the current stream is interrupted. Same thing happens if you're on speakers and plug in a headset. I doubt it's fixable (I know why it happens, but preventing the switching task from throwing the exception upstream could have extremely bad results - I'll look at it at a later date, but this is common to a LOT of Android devices.)
6. Wifi is a documented issue.
7. Swype works fine. Download the CURRENT beta. If you're using a hacked version, all bets are off. I use Swype exclusively for my keyboard on this ROM. Ditto if you're trying to sideload it from somewhere (e.g. restore from Titanium) - don't do that.
8. MMS: Documented as broken.
The thread over on Androidforums is more current than the one here, but I will endeavor to at least mirror MAJOR updates here.
richiehd said:
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
Click to expand...
Click to collapse
Yes, that was something I found with CM7. The screen flickering issue is not present. YMMV.
platypuss94 said:
* another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
Click to expand...
Click to collapse
on this note i will say it is in fact how you hold the phone. it happens to me all the time on my stock triumph. no big deal and nothing to worry about. but thank you for saying something about it none the less.
This thread is meant for (technical) discussion of OT-995, notably ICS-based (e.g. CM9 and AOKP) OS and kernel development.
Any non-technical questions/discussion belong in the general OT-995 thread.
Status quo
There's an ongoing effort bring CM9 and AOKP to the OT-995. Although neither is anywhere near complete, basic functionality (graphics/audio/gsm (non-data)/wifi/sensors) is present.
Both iuss and fonix232 currently maintain Android repositories related to OT-995. A common kernel is maintained by iuss, based on the 2.6.35.11 release by Alcatel.
Updates will likely be posted in this thread, but this topic start may not be fully up-to-date.
Source repositories
kernel: https://github.com/ius/tct_cocktail_kernel
android/bootable/recovery: https://github.com/ius/android_bootable_recovery
android/device/tct/cocktail: https://github.com/ius/android_device_tct_cocktail
(on top of the CM 'ics' branch)
android/device/alcatel/cocktail: https://github.com/fonix232/android_device_alcatel_cocktail
android/vendor/alcatel/cocktail: https://github.com/fonix232/android_vendor_alcatel_cocktail
Flashable releases
fonix232 has provided flashable builds of CM9 and AOKP: http://goo.im/devs/fonix232/OT995/ICS
(Be aware that these might not always be up to date with the repositories listed above)
Other bits of interest
iuss' slightly outdated README for his repositories.
fonix232 said:
Possibly, couldn't really boot yours though :\
Also, some more info about liblights. The tempfix works (keyboard lights up with screen), but apparently when the keyboard file is set in liblights, it won't call the keyboard function. If I set it to e.g. the notification LED, it is called, but bails out with error 13 (no access to notification LED control).
Click to expand...
Click to collapse
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
iuss said:
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
Click to expand...
Click to collapse
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens. I've logged it, every device open, every call of write_int, every device light setting, everything, and keyboard only showed up when:
a, Not the proper keyboard brightness path was given (in my case, it was the notification LED)
b, Moved the keyboard control to the lcd-backlight controller function - as it is currently.
And apparently yes, I've forgot to chown the whole LED folder's content to system
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
handy tool for making logs...
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
Click to expand...
Click to collapse
Download : dl.dropbox.com/u/2889810/apps/getlogs_v1.1.apk
Thread : http://forum.xda-developers.com/showthread.php?t=1123129
I do it by hand, but thanks ;D
maby its a good thing to copy the apk to system/app
there will be a lot of people installing the build and then complain here that some stuff dont work (also bugs u didnt even realize they where there cuz u cannot test alone)
and when u ask them for logs some of them dont even know how to do it..
fonix232 said:
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens.
Click to expand...
Click to collapse
If I interpreted things right, you mean neither was ever called? If you had wired buttons-to-keyboard it should've worked, the reason why set_keyboard_light was never called is because TCT hacked the Java framework (by making the turn-on-screen-backlight-and-buttons event turn on the keyboard light as well).
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
Click to expand...
Click to collapse
The monkey approach - I checked out the code for Nexus; it doesn't provide a battery light at all (which is probably only useful if you have a green/red led); attention and notification are routed to the same led.
The stock liblights seems to work quite well, e.g. notification (sms/mail) causes a blink, attention (USB inserted) a constant light.
Let's just copy stock liblights for now, we can rewrite/reverse it later.
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
Click to expand...
Click to collapse
Good catch. Fixed in my kernel tree (no-op instead of a null fptr call)
iuss, I understand your concerns, and most probably will stick to it, but I've already began writing liblights Actually, it's like, around the fifth revision, fifth try, and still no worky. Just finished up my test-package (ultimate AOKP-CM9 with GApps installer, will post it separately), will test that and check back.
EDIT:
Tried your new kernel, but somehow, wifi fails to connect. DHCP timeouts, etcetera.
Works fine here (and I didn't touch anything related). For reference, a built zImage.
iuss said:
Works fine here (and I didn't touch anything related). For reference, a built zImage.
Click to expand...
Click to collapse
Egh, turns out it was my fault, something frikked up with my installer. Still working on the small quirks tho
Also an idea about BT - why not use the same module that the Galaxy Tab P4 series used? They are all BCM4330, so theoretically it should work!
question is it possible to make 3 point multitouch? (or more?)
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
iuss said:
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
Click to expand...
Click to collapse
The 5306 can detect up to 5 distinct touches, but apparently either the chip was locked down to two (or via baseband, and might be unlocked in ICS), or just the communication signal is processed in a wrong way.
But nice addition with the multitouch support!
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
fonix232 said:
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
Click to expand...
Click to collapse
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
iuss said:
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
Click to expand...
Click to collapse
I don't see either, but when brightness is on manual, I have to modify the value for the keyboard lights to show up.
Performance issue
I know, my question is maybe premature.
But what about the performance. Do you feel it could be faster than the stock rom?
Maybe some quadrant test would give us some idea?
it feels amazing
I think I might know a way to have 5-point touch, but it won't be easy...
Looking at the source code of the ft5306, you can see that in the firmware upgrade part, it points to a header file: FTS0094P430_CockTail_V1d_20111123_app.h
This header is nothing else, but an actual FT5306 firmware file, dissected into bytes. Basically, they took the hexa code of a binary firmware, and pasted it into a text file byte by byte! Sounds stupid, but actually a good way to integrate a firmware into the kernel.
However, the function can be overwritten so instead it reads bytes from an actual binary firmware file, located on the filesystem. Doing that, plus acquiring a 800*480 FT5306 firmware image (so far I've only found an 1024*600 one) would result in unlocking the whole capacity of the panel!
Also gave a try at the camera HAL. I can't make it work sadly :\
What happens if you write bogus firmware to ft5306, though? :x
The panel will most probably won't work, although the firmwares are pretty similar in all the ft5x06 series.
Aaaalthough, if you reflash a proper firmware, it should work again
I have the Resurrection Remix GSI installed and it's great for both features and battery life. However I am unable to get two things working.
1) The hardware button doesn't do anything when I press it and I don't see any options in the RR section of the Settings app.
- Is there a way that I can enable this for something like, opening a specific camera app (GCam, or maybe Google Assistant)?
2) It also doesn't have double tap to wait either
- Now, I remember there being a mod in some old Pixel Experience GSI thread in this forum to enable this feature. Sadly, but the mod itself has been removed since the developer ended up modding the feature into the ROM. So I was curious if anyone remembered how to enable this feature on a vanilla GSI.
Thank you to anyone who can help!
Hi Guys,
Some of you may remember me if you had a Galaxy S9 or Note 10... I rooted my Note 10+ 5G (N976B) Last night and decided to try and have a stab at getting stock android on there by means of project treble. This is a Semi Generic System Image - meaning it's been/being enhanced specifically for our note devices and less focused towards being cross compatible with other devices.
If you have already tested the existing treble roms you'll know that the back lighting doesn't work and you can't adjust brightness. I've had a play around and I've got a working Android 10 AOSP build with fully working backlighting. I thought I'd share as I'd seen a few people who said they can't get GSI's working.
Download System Image
Gapps are included, the image is not rooted. You can flash Magisk yourself.
How to flash:
Make sure you're on a stock based rom (and rooted/twrped) Dr Ketan posted a good guide for this.
Download the System Image above
Reboot to TWRP
Select Wipe
Slide the bar across the bottom of the screen
Go back to the main TWRP menu and select install
Press "Install Image" at the bottom right.
Select the system image you downloaded and swipe to flash.
Once the GSI boots perform another reboot - for some reason the navbar doesn't start up on first boot.
What's working and not working:
Obviously you lose S-Pen functionality, but can still use it as a stylus. You also lose the ability to use your telephoto and telescopic lenses.
UltraSonic Fingerprint isn't working at the moment, but I'm looking into fixing that.
How can you help me?
Let me know how it's working for the different device models. People on other versions please can you let me know your device vendor fingerprint. (to do this On your device, in adb or Termux app use this command: getprop ro.vendor.build.fingerprint)
Credits:
phhusson - for all the project treble work, this is all thanks to him.
Please please support N976n. ???
xshaowenruix said:
Please please support N976n.
Click to expand...
Click to collapse
It should work, it's semi generic. Give it a try and let me know if it works.
If it doesn't I'll need your device fingerprint.
Good work!
Nice ... you stared to work whit the N10+ , still remember havoc in my N9 was a great time , keep goin Fox
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Welcome aboard
carandcar said:
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Click to expand...
Click to collapse
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
CodeFox said:
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
Click to expand...
Click to collapse
I have N975f. I understand what you mean about keeping it pure. I just like to be able to change the look up. ? Thank you again for bringing this to us.
I managed to get fingerprint working
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Jamjarr said:
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Click to expand...
Click to collapse
Hmm, Interesting. I will look into it. Thank you.
Thanks (and a quick question)
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Would this gsi theoretically also fix the s10's brightness issue too?
CodeFox said:
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Click to expand...
Click to collapse
It did this to me too when I was first setting up the phone, but after it was all set up, I went into the settings to try again, and it worked that time. It didn't show the fingerprint logo during this setup (and it still doesn't on the lock screen), but after a couple tries I was able to estimate correctly where the sensor was. Interestingly, the fingerprint logo does come up in the password manager app I use when I go to unlock it.
Not sure if there are logs that would help or if recording my screen while adding a new fingerprint would be informative, but I'd be happy to do either if that helps you debug in some way.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
DBDPCG said:
Would this gsi theoretically also fix the s10's brightness issue too?
Click to expand...
Click to collapse
What's the issue with the S10? The backlight doesn't work?
CodeFox said:
What's the issue with the S10? The backlight doesn't work?
Click to expand...
Click to collapse
As I've heard, haven't tried it yet though
DBDPCG said:
As I've heard, haven't tried it yet though
Click to expand...
Click to collapse
For what it's worth, all the other GSI's I've tried for the Note 10+ weren't able to adjust the backlight; this is the first one where it just worked. I don't have an S10 to try this out on though, so I have no idea how this ROM would run on it.
LTE working despite phone claiming 3G
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
saghm said:
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
Click to expand...
Click to collapse
Go into your network settings and change the default connection from 3g to LTE/4G/3G.
For some reason it seems to default to 3g preferred.
Tap, Tap is a port of the double tap on back of device gesture from Pixels running Android 12 to any Android 7.0+ device*.
Tap, Tap provides over 50 actions that can be run from double or triple taps on the back of your device, including:
Launching an app
Launching a shortcut
Toggling the flashlight
Simulating button presses, such as home or back
Running a Tasker task
Quick Tap to Snap**
... and many more!
The gesture can also be fully controlled, to only run under certain conditions, or run different actions in different scenarios; such as only when an app is running, the screen is off, or when listening to music (many more options are available).
The sensitivity and response of the gesture can be controlled, picking from 8 "models", trained for devices ranging in size from 5.7" to 6.3" in height, as well as finer control of the sensitivity of gesture detection, meaning there is a configuration that will work well for most devices.
Tap, Tap also tries to be easy on the battery, only running the gesture detection when required, and integrates with the "low power mode" available on select Pixel devices, otherwise using the lower-power machine learning capabilities of devices, where available.
* Your device must have an accelerometer and gyroscope.
** Requires a compatible Pixel device or root, see this page for more info.
Screenshots:
Example video, showing launching the camera on double tap
Changelog said:
Version 1.6.1
- Fixed crash on Android 14 Beta 3
- Updated dependencies
Version 1.6
- Added support for Android 14 DP1
- Fixed Low Power Mode on some Android 13/14 builds
- The "Apps" requirement now displays the selected app on the requirement list
- Removed checks from switches since it broke the animation
Version 1.5:
- Added new Samsung model from RegiStar
- Added new action to simulate rotating the device
- Added support for LG DualScreen devices for foldable gate
- Fixed a number of crashes
- UI tweaks
Version 1.4:
- Fixed Native Mode on Android 13, and as a result it now requires Shizuku or Sui. This is because of restrictions to the READ_LOGS permission on Android 13
- Added Notification Permission prompt for Android 13
- Updated Material switches to newer Material You style
- Updated dependencies
- Added touch on screen action, thanks mauri870
- Updated Traditional Chinese translation, thanks cracky5322
- Fixed incorrect button action during setup
- Fixed crash on Android 10
- Fixed incorrect notification for gesture actions
Version 1.3:
Introducing Native Mode, a new low-battery usage mode for Pixels with official Quick Tap support. This mode, similar to the existing low-power mode, uses the system component, but does so without needing root (on Android 13) or a constantly running Shizuku service (on Android 12). To set it up, you will need to use ADB or root once to grant a permission, after that it will run without further actions being required.
Please note that Native Mode does not work while the screen is off, and you may find triple tap is harder to use with it enabled. Both of these are system restrictions and cannot be worked around.
In addition, 1.3 fixes some crashes, updates translations, and fixes Quick Tap to Snap from the lockscreen.
Version 1.2:
Tap, Tap v1.2 disables the Tensor Low Power Mode by default as it was causing issues with some devices not working with the gesture.
If it was previously working for you on 1.x, and you experienced battery improvements, you can re-enable it in the advanced settings.
Low Power Mode on supported Pixels with Shizuku or Sui is not affected by this change.
- Added missing alarm permission
- Fixed more app shortcut crashes
- Improve foldable gates
- Added monochrome icon for Android 13
- Translation updates
Version 1.1:
- Fixes for Android 13
- Fixed app shortcut related crashes
- Fixed service starting on boot even if it's disabled
- Fixed crash on start on Android 7.0
- Added Do not Disturb enabling action, thanks Kylian Meulin
- Updated translations
Important: If you are on Android 13, you MUST now use Sui to use Low Power Mode (Sui requires root). This is due to platform restrictions, there is no workaround.
Version 1.0.1:
- Fixes for various crashes including Snapchat, App Shortcuts and network issues.
- Improvements to device specs lookup for model recommendation
- Improvements to notification & quick settings expand/collapse actions
- Actions & Gates that are unsupported will now give a reason why they are
- Added Battery Saver gate
Version 1.0 is a full rewrite of the app, from scratch. It contains a brand new UI, a number of new actions and gates, and implementation of the Android 12 'Columbus' gesture code and models, including a new Low Power Mode for Pixels.
You can read more here: https://medium.com/@KieronQuinn/tap-tap-v1-0-restarting-from-scratch-2b87c241d176
Click to expand...
Click to collapse
Download:
Version 1.6
GitHub:
https://github.com/KieronQuinn/TapTap
Reporting Issues & Feature Requests
If you have encountered a crash or error, please make an issue on the GitHub Issues page. For crashes, include a crash report, which Tap, Tap should create for you and show a notification after a hard crash (enable the option on the "More" page first if you have disabled it). Before making an issue, make sure it has not been reported before, and does not fall under the "service killed" pinned issue, as those will be closed and ignored.
To request a feature, either make an issue stating "Feature Request", or post a reply in the XDA thread. Note that only relatively simple features will be considered, anything more complex including toggling specific system features should be done using the Tasker capabilities of Tap, Tap, as the app is not meant to be a Tasker replacement.
I just installed it on my Pixel 4 XL and I'm really impressed by its accuracy. Also the UI looks very nice, good job!
I tried it on a Xiaomi mi8, works great
Wow, this works surprisingly well on OnePlus 7Pro, even with a case on. Although sometimes I'll go on a run of it working 10x times in a row, and then it won't work for the next few, and then go back to working again.
Currently using the Pixel 4XL model as I think it's the closest out of the three. It definitely needs more of a deliberate tap - tap instead of a super quick double tap to be more accurate, but that's not a problem at all.
Super excited to see what (if any) improvements can be made to the model, or sensitivity in the future.
Sent from my GM1917 using Tapatalk
Worked like a charm on the Mate 20 Pro using a Spigen case. This is awesome.
Tasker Integration
Can't wait to see the Tasker Integration to open up the whole new level of potential.
Thanks for the app!
mi_guel said:
I tried it on a Xiaomi mi8, works great
Click to expand...
Click to collapse
Same on Redmi Note 8 Pro
Works well on my xperia 1! Thanks
Id love for this to work when the phone is locked. Perhaps with root or magisk? Definitely willing to pay
Working Perfectly on Mi A2 Lite Major thanks to such an awesome Developer
Nice work, installed on my Galaxy Z FLip and it works great, can you add the ability to double tap and choose a shortcut too
THank you for the greatwork!
Trying it with my s10 exynos and it works great, little weird at times with a case but it still works 90% of the time
TrustAugustus said:
Works well on my xperia 1! Thanks
Id love for this to work when the phone is locked. Perhaps with root or magisk? Definitely willing to pay
Click to expand...
Click to collapse
Disable the screen off gate lol
And turn on the wake device up feedback if it's an app launching and not something that will work with the screen off
dallasnights said:
Nice work, installed on my Galaxy Z FLip and it works great, can you add the ability to double tap and choose a shortcut too
THank you for the greatwork!
Click to expand...
Click to collapse
Double tapping might not be possible, the tensorflow model appears to be for a single tap only, but I might be able to figure something out eventually.
Shortcuts as in like launcher shortcuts to call someone or open Maps directions? Probably will add that.
Tried on my Redmi Note 7 Pro using Havoc. The default command seemed to work but I changed it to back button simulation, and it doesn't work. My phone vibrates, telling me that Tap, Tap recognized my tapping but the command wasn't executed.
EDIT: lock screen works
Sent from my Redmi Note 7 Pro using XDA Labs
adriansticoid0312 said:
Tried on my Redmi Note 7 Pro using Havoc. The default command seemed to work but I changed it to back button simulation, and it doesn't work. My phone vibrates, telling me that Tap, Tap recognized my tapping but the command wasn't executed.
Click to expand...
Click to collapse
Do any of the other actions other than the default setup work? That would help rule out whether it's an issue with back or an issue with actions in general on that device
Quinny899 said:
Disable the screen off gate lol
And turn on the wake device up feedback if it's an app launching and not something that will work with the screen off
Click to expand...
Click to collapse
Sorry I was unclear. It is disabled. But from my experience in the past with apps such as button remapper I have been unable to get screen off commands to work properly. In that instance using volume buttons, it was possible. But not for dedicated camera keys etc.
Now, with the gate disabled, flashlight, Assistant do nothing when the screen is off. When it is on but in the lockscreen it still doesn't work. The phone is unlocked work trustedagent,too.
Works really nice on a Pixel 3. The app is really well made and I love the design.
Quinny899 said:
Do any of the other actions other than the default setup work? That would help rule out whether it's an issue with back or an issue with actions in general on that device
Click to expand...
Click to collapse
Lock screen and flashlight works.
Sent from my Redmi Note 7 Pro using XDA Labs
Tried with my OnePlus 7 Pro, works excellent so far!
Not working on Oppo Reno 10x Zoom
EDIT:
Works - I found the spot!
Works using PiXL 4 and Pixl 4 XL