As reported in multiple places on the forum, stock ICS ROMs do not come with the CRT-Off effect available, although the code is there and lots of existing mods already exist to be able to turn it on.
The implementation, however, contains a glitch and every once in a while the full screen image will blink right after the beam collapses.
I have managed to apply the fix to the Sammy's custom library that implements this, even though the source code is not available. (this wouldn't be possible without the good folks on CM9, though!).
The discussion that lead to this work can be found here, on the awesome JKay mod. BTW, if this fix is useful to you, do me a favor a buy that man's Deluxe app (it's really a favor you're doing to yourself, not me ).
For any ROM cookers, MOD developers, or end-users, I leave the patched file and a few instructions to make sure the provided lib only changes the flicker part. This is because I have performed the changes on the file shipped on XWLP9, and if other different files exist in other builds, it's more convenient to apply the fix there instead of using the lib from a different ROM and possibly lose some other improvements or fixes applied by Samsung.
Please check the Readme file in the archive for instructions on what to confirm and how to apply the change, and let me know if there's any question or if you have a different base version.
EDIT:
The library has been updated to handle CRT-On effect as well. You can safely replace it with the attached version, although you'll need to have a mod to activate the CRT-On effect as well.
If you want to install a standalone patch to activate this, have a look at this post and follow the instructions.
Technical notes
The code has been revised to display 8 frames when turning on - as opposed to 24 when turning off - in order to have a faster response. This is however still dependent on the time taken by the kernel to wake the CPU, before drawing can begin (currently about 1s). This delay will not happen if you don't wait long enough after turning off, as the CPU will not enter deep sleep.
Changes from Kamma have also been applied, in order to have a similar effect when turning On - "normal" screen colors instead of random color spikes. This might be barely noticeable due to the animation speed.
EDIT2:
No more issues with the library, it now works perfectly with Youtube playing videos, etc. Also the CRT-On effect is now very smooth (although faster than CRT-Off, on purpose).
Major kudos to rovo89 for turning an initial hack to fix the glitches in a polished final product!!!
Be aware that this just contains the library for the effects to work properly. You'll still need your ROM to be modded to activate them (instructions included in this zip file), or, better yet, install rovo89's Xposed Tweakbox module which overrides the behavior without replacing any files and should work even with non-stock roms.
Out of the box solutions for getting the CRT effects
Tweakbox by rovo89 (and a bit of help from myself) - works for pretty much all stock roms and derivatives, odexed or deodexed. It's even working for S3, since it contains a patched file from that model.
If you're using Deodexed XWLPG, you can also go to this post by The Undertakerr and fetch a flashable zip that contains everything that's needed to have CRT_On and CRT_Off effects always active.
Works great on Wanam V11.7 (LPD)
Wow thanks a lot for this
Enviado desde mi GT-I9100 usando Tapatalk 2
Thanks man!
Applied JKay's CRT mod just today and noticed the bug, now you fixed it!
I try on Turkbeyrom V9 Lpd. Its working perfect.
Wysłane z mojego GT-I9100 za pomocą Tapatalk 2
@ Tungstwenty
... Carried over from jkays thread,
You're right i didn't have any anything to turn crt on, i presumed it enabled it by default, since i flashed a similar fix from another thread and it enabled it straight off.
So hopefully jkay includes it in his mod and 'jobs a goodin'
Cheers
Sent via courier pigeon
Works perfect on Wanam V11.7.
Thank man!!
This is working great, also on LPQ. I also thought about patching the library directly, but didn't know where I could get the replacement code from. Great work!
I have been working hard today to bring some binary patching functionality to Xposed. Finally, I think I was successful. Learned some new things, like modifying a different process' memory. That will make it possible to patch the library on the fly, just if the MD5 sum matches etc. I believe this will make it easier to use for those who are not as experienced with adb/SSH/...
rovo89 said:
This is working great, also on LPQ. I also thought about patching the library directly, but didn't know where I could get the replacement code from. Great work!
I have been working hard today to bring some binary patching functionality to Xposed. Finally, I think I was successful. Learned some new things, like modifying a different process' memory. That will make it possible to patch the library on the fly, just if the MD5 sum matches etc. I believe this will make it easier to use for those who are not as experienced with adb/SSH/...
Click to expand...
Click to collapse
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Works perfectly well on LPF build.
I'm wondering whether its possible for you to make a flash able version?
SGSII GT-i9100 via Tapatalk II
I pasted it using romtoolbox but it didnt work so I rebooted and it works !!
Thanks
Tungstwenty said:
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Click to expand...
Click to collapse
Indeed, I'm using the files in /proc for patching. Plus "ptrace" to manipulate the /system/bin/surfaceflinger process, after I noticed that the library isn't used directly by any process started by Zygote. And for the patch file, I'm using bsdiff and a MD5 sum comparison.
If anyone would like to try out, here are betas of the upcoming Xposed framework and the Tweakbox. Installing instructions are in the linked threads. Afterwards, you can check "Patch libsurfaceflinger.so" in the Tweakbox settings, which will become effective after a reboot (but doesn't require replacing any files).
Please note that I have also added new helper methods for developers. Let me know in case setting the statusbar clock color is not working for you.
Tungstwenty said:
Wow, that would be yet another massive leap in your framework. Patching e.g. native libs on running processes from within java would really be awesome
If you've reached that stage already, you probably already know that "cat /proc/nnnn/maps" yields interesting information on where each library's segment is mapped. Other pseudo-files on that path also hold tons of information just waiting to be explored and hacked
Click to expand...
Click to collapse
I've been testing your lib for 2 days now and as i told you in Jkay's thread flicker bug is gone
The only thing i noticed,happened only 2 times ,i had no crt off effect at all.
The screen locked as in stock.
Thank you for this
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
This, Tungstwenty, is a huge step forwards in development of the I9100. Even on Gingerbread the CTROff effect wasn't as beautiful as it is now!
CtrON is also available allready for ICS 4.0.3, only not for our device.
XDA member Kamma made it work on the Galaxy Nexus, and also posted the sources for it.
It involves changes in the libsurfaceflinger.so and in the services.jar.
Since you seem to be able to make changes in the .lib, my hope is on you, perhaps you could also bring the CRTON to the I9100 with ICS!
Sources+ info you can find in this thread:
http://forum.xda-developers.com/showthread.php?t=1490127
Thanks in advance for looking into it and bringing us a perfect CrtOff!!!
The Undertakerr said:
This, Tungstwenty, is a huge step forwards in development of the I9100. Even on Gingerbread the CTROff effect wasn't as beautiful as it is now!
CtrON is also available allready for ICS 4.0.3, only not for our device.
XDA member Kamma made it work on the Galaxy Nexus, and also posted the sources for it.
It involves changes in the libsurfaceflinger.so and in the services.jar.
Since you seem to be able to make changes in the .lib, my hope is on you, perhaps you could also bring the CRTON to the I9100 with ICS!
Sources+ info you can find in this thread:
http://forum.xda-developers.com/showthread.php?t=1490127
Thanks in advance for looking into it and bringing us a perfect CrtOff!!!
Click to expand...
Click to collapse
It is not perfect, please check my post above and confirm..
mzeshanhakeem said:
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
Click to expand...
Click to collapse
Tried to reproduce this a couple of times, but it always worked fine. I turned the phone on, unlocked (using WidgetLocker), then didn't do anything for few seconds and pressed the power button to lock the phone. The effect is showing for me.
mzeshanhakeem said:
It is not perfect, please check my post above and confirm..
Click to expand...
Click to collapse
I cannot confirm the behaviour you have, I'm sorry. It's nothing new. The thing you describe also happened before the change made to libsurfaceflinger.so by Tungstwenty.
It even also happened on Gingerbread!
Sometimes the lockscreen also freeze for a few secs, but that's also not because of this change. You can read about it in the Siya kernel thread, seems to be related to the newest Siyakernel...
The Undertakerr said:
I cannot confirm the behaviour you have, I'm sorry. It's nothing new. The thing you describe also happened before the change made to libsurfaceflinger.so by Tungstwenty.
It even also happened on Gingerbread!
Sometimes the lockscreen also freeze for a few secs, but that's also not because of this change. You can read about it in the Siya kernel thread, seems to be related to the newest Siyakernel...
Click to expand...
Click to collapse
That may be the reason.
I am on Wanam v11.8 with CF Root Kernel.
mzeshanhakeem said:
Please check and confirm guys..
Unlock screen, do not do anything. Just wait 7-8 Seconds without touching on the screen and then turn off screen, there will not be any CRT Off effect.
Click to expand...
Click to collapse
I cannot reproduce this also.
Tried just turning on screen and leave it alone, it will automatically CRT Off after 10s with my current settings. If I press Power 1 or 2 seconds before that, it still does the effect.
Also tried it with actual unlocking (going to the home screen), and effect also displays when turning off after 8s idle.
Does it always happen to you?
Running on XWLPF with JKay and Siyah 3.2.6.3
Related
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb
welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!
arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless
welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......
i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know
Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!
Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!
Reserved as well!
Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!
Please make the thread for GSM also.
TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose
PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse
CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb
BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.
Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well
First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?
UPDATE 4
Hello all,
Pending a new release for this ROM, I will stop supporting the "0.3" version originally posted.
I would like some help deciding cosmetics & features next release before it goes live. Please complete the following brief survey:
http://www.surveymonkey.com/s/VJRLWRZ
A lot of fixes and changes have been made and requests have been accounted for as long as they do not deviate from the nature of this ROM being clean, functional, stable, good-looking, and ready to be a base for future devs. The appearance will be very AOSP-ish but with traces of TouchWiz.
Heads up: there will be no XLoud\Beats Audio by default. We have enough audio issues as it is and these are IMHO not any better than using DSPManager (aside from having the cute Sony\Beats branding stamped on them).
I'm not releasing anything until I fix the damn call echo issue ...worst case scenario I will workaround it by keeping Noise Reduction off. But I want to fix it
Q&A: http://forum.xda-developers.com/showthread.php?p=24253640
General questions? post in the above link...it will help me keep track better
^^
I no longer wish to have two seperate topics. So post here...but wait till the next release before you do
First of all, thank you to Racing19969 and anybody else associated with the Skyrocket ICS port...you made this possible.
Also want to thank CyanogenMod (<3) and the original author of DSP Manager (will find credits tomorrow) from which I borrowing DSP Manager for this ROM
The goal: to make a CLEAN, no frills alien TouchWiz + ICS rom. Its not meant to be exciting or have a crazy amount of hacks in it. In fact as of right now, the only packages added from the community are SuperUser and DSP Manager. And I don't plan on changing that.
Current status is...the ROM is running and its running QUICK. But there are some minor issues to be worked out and some beautification to be done.
The priorities:
Stability
Friendliness
Battery Life
If you are going to comment without constructive criticism, then just look away from this thread. The ROM is what it is. If you are going to install it, I would appreciate pointing out as many bugs as you can
For right now (temporarily): I did add the wonderful, feather-weight Zeam Launcher alongside TouchWiz...this is because I had issues with TW force closing on me early on in the modification process. So until more progress is made on this ROM, I've decided to keep it in there in such an event that TW decides to be unhappy and constantly force close.
A *lot* of bloatware was removed, especially from AT&T and some of Samsung's own social/media/diary/etc packages. I want this ROM to be STABLE, fast, and clean.
Next release ETA:VERY VERY SOON. NOW THAT AUTO ROTATE WORKS :-D
That being said, there are still issues to be worked out. Here is the list of changes made right now:
Added DSPManager from update-cm-9-20120330-NIGHTLY-galaxys2-signed, not functional ATM
Added Gallery, Mms, and Shutdown from GT-I9100 XWKI4 ROM; This fixes the shutdown issue, the Gallery landscape resize issue, and the delete SMS thread FC issue
Also added Browser from GT-I9100 XWKI4 ROM; not only is it more stable but the Search icon is fixed in its place and it has more features
Added apns-conf.xml from above CM9 nightly
International Galaxy S2 boot animation (AT&T anim is hideous)
Removed many many bloat; I'll try to compile a better list later
Added latest version of Polaris Office from T-Mobile ROM...It's a simple, lightweight, and pretty good doc editor/viewer
Already rooted
TODO:
Merge racie's unsecure Skyrocket Kernel COMPLETE
^^ Transform samsung boot animation to a ZIP to work with above kernel
Remove traces of Software Update COMPLETE
Put back the 2G - 3G / band select setting in our Settings menu Priority
Identify as SGH-T989 in build.prop
Removing AT&T contact sync wizard from Contacts.apk, also restore Contacts to the dialer tabs IN PROGRESS
Revisit shutdown issue IN PROGRESS
CWM flashable patch for the Skyrocket folks
Remove AT&T VM icon in Phone dialer
Fix T-Mo Voicemail indicator SMS Priority
Fix Auto-Rotation (perhaps by modifying Framework \ WindowListener) FIXED FOR NEXT RELEASE / PATCH AVAILABLE NOW
Remove remaining traces of AT&T Bloatware
Modify TouchWiz default home screen XML so that widget_service_v0.1.4_shared.apk can be removed from the system/app folder entirely prior to emptying the home screens COMPLETE
Remove debugging / service testing apps
Wi-Fi calling for T-Mobile
Change ugly status bar icons to stock ICS style; remove AM/PM indicator, and remove carrier label from status bar itself IN PROGRESS
Optimize PNGs, zipalign
Call echo and RIL issues; improve call quality IN PROGRESS Priority
Add quick toggles due to demand IN PROGRESS
Set up bug tracker website
Default Market to Play Store
A "Tweaks" menu to make some important modifications but without necessitating manual editing or downloading a lot of stuff from Market
PRIOR TO INSTALLING: Make sure you superwipe with DARKSIDE's SUPERWIPE script.
And finally...
the link (flash with CWM):
http://dl.dropbox.com/u/50663221/CleanICS0.3.zip
MIRROR:
http://www.4shared.com/zip/9iWiyyMY/CleanICS03.html
Thank you to markusf21 for providing the above mirror. Bandwidth costs money, so please give this user a thanks!!
PS, my personal opinion...install the Telus radio. no echo issues thus far. But if you don't know what a radio is....don't do it.
Update: I have big suspicions that this is a RIL or qualcomm audio config issue. It is now the priority problem which I will look to tomorrow..
Enjoy
Update coming tomorrow..
For today I am tired!
Hopefully I can get this one to boot. Raver's just gives me booltloops to eat. We'll give this a run. I'll report back.
Edit: booted right up and is going well. Nothing too crazy yet. Will keep you posted.
Youtube played well and video was right on. I could actually hold it in landscape and watch video with not much effort.
>>DARKSIDE
the first boot may take a few min as this is Deodexed
Also, nice to see a fellow P999er here
I have been running the port for the past 3 days and the only issue I have is the rotate and I know that's a kernel issue but that port took many flashes and reboots. Let's see if this one is easier to install and I'll report later.
Edit : I always use darkside wipe just like on my transformer there some kind of wipe just like it and I'm so glad that the gs2 has it too.
Sent from Samsung Galaxy S II
It's important to to siperwipe. Darksides script works perfectly everytime, but prior to using it it took me many attempts to flash the leak. I am looking into hacking usermode android into invertig the kernels auto rotation parameters. Dirty hack but I believe it is possible
by looking at the change log I think you are on the right track! I do have one question, on the ics skyrocket leak, I noticed there is a lot of freezing and watching streamed videos is damn near impossible it lags beyond belief, so I was wondering if you had a chance to take a look at some streamed videos.
Sent from my SGH-T989 using XDA
Have not tried any streaming but youtube...youtube works well
Edit: HQ working perfectly on youtube as well
Link is down now can anybody mirror?
Sent from my SAMSUNG-SGH-T989 using xda premium
Somebody offered me to mirror via PM. I just asked him to help me out
Edit
much gratitude to markusf21 for helping me out
Link coming in 15min
MD5 sum: d5206397a40483cd017e3c3295f8a1c3
It really works well ty. One question the ics youtube is ridiculous is it possible to bring back the GB app?
Sent from my t989 --- SAMSUNG-SGH-I727 using XDA
Any chance we can see some ROM screenshots of changes?
Dead link can you please provide a mirror
Mirror on the way...
Screenshots I will try my best to do tonight, although I do not think I can until tomorrow (~12 hours from now since we're all in different timezones)
I'm not into any drastic theming, so there is not much specialty here. I like clean and simplicity....I cannot BELIEVE AT&T and Samsung even plan on releasing the current ROM they have for Skyrocket. It's bloated to hell.
EDIT:
If anybody can confirm the following MD5 with the mirror:
d5206397a40483cd017e3c3295f8a1c3
I appreciate it. I just want to make sure I calculated the right one and that the mirror is also the same.
raycaster3 said:
Hopefully I can get this one to boot. Raver's just gives me booltloops to eat. We'll give this a run. I'll report back.
Edit: booted right up and is going well. Nothing too crazy yet. Will keep you posted.
Youtube played well and video was right on. I could actually hold it in landscape and watch video with not much effort.
>>DARKSIDE
Click to expand...
Click to collapse
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once
sarni84 said:
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once
Click to expand...
Click to collapse
Well since our auto rotate is broken, I just turned it on and physically put the phone in portrait mode. LOL
And agreed at Camera Zoom FX. Like it a lot. If the autorotate fix doesn't work out, I will compile an ICS camera locked to landscape mode**.
@Skorpion_
I will look into it, hopefully in the next 24 hours.
yaldak said:
Mirror on the way...
Screenshots I will try my best to do tonight, although I do not think I can until tomorrow (~12 hours from now since we're all in different timezones)
I'm not into any drastic theming, so there is not much specialty here. I like clean and simplicity....I cannot BELIEVE AT&T and Samsung even plan on releasing the current ROM they have for Skyrocket. It's bloated to hell.
Click to expand...
Click to collapse
No worries man take your time you earned it buddy!!
Sent from my SGH-T989 using XDA
sarni84 said:
How did u get youtube in landscape? I have the hacked hd ics youtube pushed into system apps . It works great but no landscape.....is it the youtube that comes with the rom? Oh and for a camera fix use camera zoom fx... it will actually show pics the right way in gallery and send to people the right way too. For portrait shots just hit menu and rotate once
Click to expand...
Click to collapse
I started the video then turned on screen rotation then held in vertically and slowly moved to horizontal and voila. I used the YouTube app that came in the rom.
The only real gripe I have right now is that the sideways scrolling16 panel toggle (thanks lidroid & RaverX3X) and the folders ui in gtab simiclock is pretty sticky, from lack of a better word. I'm sure it's due to the rotation issue. Looking good so far. Adwex hauls ass on this rom.
Oh yeah and vignette is great for pics too, alas youbhv to go into gallery and rotate them. Snaps em quickly tho. No delay like the stock camera.
>>DARKSIDE
raycaster3 said:
I started the video then turned on screen rotation then held in vertically and slowly moved to horizontal and voila. I used the YouTube app that came in the rom.
The only real gripe I have right now is that the sideways scrolling16 panel toggle (thanks lidroid & RaverX3X) and the folders ui in gtab simiclock is pretty sticky, from lack of a better word. I'm sure it's due to the rotation issue. Looking good so far. Adwex hauls ass on this rom.
>>DARKSIDE
Click to expand...
Click to collapse
Ok gotcha now...
if this is from ics leak from our skyrocket then im just gonna flash this .. it'll make life easier since somethings like rotation issue won't be there haha.. good job dev. and will wait for your update..
edit: also if u need a theme im working on fully revamped ics theme which will blow minds let me know im on i727 forum
The reason for this little hack is the fact those 2 pop-ups can become an extreme double-annoyance while driving in hot weather. Imagine, your battery is below 15%, yet scorching hot, beyond the charging cut-off threshold. Connect a charger and you get bombarded with the "charging paused, battery temperature too high" pop-ups. Disconnect it and you get a low battery ones. This little patch deals with the issue by simply disabling the annoying pop-ups. It also disables the annoying battery full notification.
Please note, this doesn't modify any functionality, it just disables the pop-ups. The battery will not and should not charge when overheated.
Instructions:
Download and unpack "BatteryPatch.zip", you should now have "Patch.js" jscript along with the "utils" directory.
Fetch your "/system/app/SystemUI.apk" from the device, place it in the same directory, along with the "Patch.js".
Apply the patch by launching "Patch.js" and push the patched SystemUI.apk back to the device.
Updates:
Not every ROM seems to have the battery full notification and/or battery overheating popup. Patching those is now optional, the script will show a warning in case it fails to patch those instead of erroring out completely.
There are some ROMs out there with showLowBatteryWarning method looking somewhat different from what i've seen on my S3. In order to try & let the patch work on more ROMs, the showLowBatteryWarning method is now being bypassed entirely. Hopefully, no ROM does anything important inside that method, besides showing the annoying low battery popups. In any case, as usual, you use the patch - you take the risk.
PS: For those willing and able to apply the patch manually, download the second zip and do a 3 way merge.
===> reserved <===
Nice mod...just added it to my rom.. purposely drained the battery...no notification pop up (hopefully won't get the temp warning anyway)
Lovely work
Already given 8 thanks today...I will come back!
_neutron_ said:
Nice mod...just added it to my rom.. purposely drained the battery...no notification pop up (hopefully won't get the temp warning anyway)
Lovely work
Already given 8 thanks today...I will come back!
Click to expand...
Click to collapse
Thanks. Temp warning should not be there any longer, too. But the rest of them (bad charger, overcurrent, stuff like that) are still there, i don't think killing those is a good idea.
The reason i did this was primarily the temperature warning. I've been looking all over the forum on how to disable it, but couldn't find any info, so i though, "what the hell, i can find it myself, it's not such a big deal"... during the search i've noticed the low bat one, too, and though "hmm, i hate that one too, lets kill it as well".
Thats about it.
Just patched and tested the full battery notification as well, first post updated.
Lovely, gonna test this when I get home
Thanks for the update
sorry to sound like a total noob, but im completely new to apktool. was reading up on it and trying it, but im slightly confused. what options do you chose exactly when decompiling? i couldnt find the power smali file after decompiling
There are plenty of explanations/tutorials on this around the forum. About not having the smali after decompiling... any chance your rom is odexed? In this case you wont be getting any smali files, cause all the code is in the odex file, not the apk. You will have to deodex it in this case and, possibly, reodex it before placing it back on the device (not sure about it, specifically i am unsure how the odex dependecies work).
Sadly, i cannot provide a ready to use apk, there are too many versions being in use, especially considering the 15 toggles mod, the battery icon mod as well as many other visual mods also patch stuff inside this apk, increasing the number of variations even further. So, sorry, no ready to use apk.
Is there a flashable file?
Sent from my GT-I9300 using Tapatalk 2
baste07 said:
Is there a flashable file?
Click to expand...
Click to collapse
Nope, and it is extremely hard to make. In fact, impossible, with the currently available CWM tools, as far as i know. It would be "for ROM version <insert_version_here> with 15 toggles and circle battery", "for ROM version <insert_version_here> without 15 toggles and green battery" etc etc etc kind of variations, and as i already mentioned, i doubt this is a viable option.
Anyone can prove me wrong and provide a way of writing a CWM script that would decompile (deodex if needed) an existing apk, apply a patch, recompile it and than replace it ? Out of all the things needed, i only know how to do the "replacing" part
Can i ask a massive favour?
im now havin problems with my systemui in regards to it recording the changes (decompiling & recompiling - i think i have an issue with my pc but i cant figure it out)
Could you apply the changes to the attached file for me?
InfX said:
There are plenty of explanations/tutorials on this around the forum. About not having the smali after decompiling... any chance your rom is odexed? In this case you wont be getting any smali files, cause all the code is in the odex file, not the apk. You will have to deodex it in this case and, possibly, reodex it before placing it back on the device (not sure about it, specifically i am unsure how the odex dependecies work).
Sadly, i cannot provide a ready to use apk, there are too many versions being in use, especially considering the 15 toggles mod, the battery icon mod as well as many other visual mods also patch stuff inside this apk, increasing the number of variations even further. So, sorry, no ready to use apk.
Click to expand...
Click to collapse
ah that explains why there is no smali file. thanks for the help!
I also cannot get this mod to work, wishing easier method coming soon, like one zip file thru recovery or similar... i dont have patience to this sorta things.
Sent from my GT-I9300 using xda app-developers app
_neutron_ said:
Can i ask a massive favour?
im now havin problems with my systemui in regards to it recording the changes (decompiling & recompiling - i think i have an issue with my pc but i cant figure it out)
Could you apply the changes to the attached file for me?
Click to expand...
Click to collapse
Done. Enjoy.
GalaxyS3man said:
I also cannot get this mod to work, wishing easier method coming soon, like one zip file thru recovery or similar... i dont have patience to this sorta things.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Well, if you know of someone that could have possibly coded an infrastructure for doing this kind of patches onboard, automatically, i would be glad to get pointed to the right direction, and will integrate it there. Currently, i don't know of any.
Seriously, though... is it possible to baksmali in recovery mode somehow ? Can one run patch, sed and similar utilities there ? If yes, can i see an example ? Cause if that's possible, it can make a "flashable zip" for stuff like that possible.
hmm, so if i have these files in my app folder:
systemui.apk
systemui.odex
I cannot just add/replace the code as described?
reprazent said:
hmm, so if i have these files in my app folder:
systemui.apk
systemui.odex
I cannot just add/replace the code as described?
Click to expand...
Click to collapse
You can deodex, patch the smali while having it handy during deodexing, and, possibly, reodex it back into an odex file and replace just the odex. Never did it myself, though. I find odexed roms to be too much of a hassle while modding stuff to use those.
Is it ok if i ask help too?
InfX said:
You can deodex, patch the smali while having it handy during deodexing, and, possibly, reodex it back into an odex file and replace just the odex. Never did it myself, though. I find odexed roms to be too much of a hassle while modding stuff to use those.
Click to expand...
Click to collapse
I been trying for days...help, i go crazy with those popups
Thats what i have on my rooted S3 I just like Omega rom, tried several others non Samsung based aswell.
Sent from my GT-I9300 using xda app-developers app
GalaxyS3man, your apk is NOT odexed. Took me barely 2 minutes to apply the patch. Here we go...
PS: TBH, i've been under impression people on XDA are perfectly familiar applying and/or finding out this kind of stuff, really
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
not sure how increasing the refresh rate helps battery?
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Im getting bootloop when i tried itt on P
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Which dtbo.img did you use as well?
Don't try it on Android 10, it should work only on Pie
So does he mean that we can also get 84hz screen on pixel phone...?
DvLAx3l said:
Don't try it on Android 10, it should work only on Pie
Click to expand...
Click to collapse
I can't even get it to work on pie tho lol
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
You used the dtbo.img from the mi9 thread that you linked? For me when I flash the dtbo.img the app just closes and nothing appears to happen. You were extract the boot.img for magisk or is it required for the mod as well? Thanks.
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
melodystyle2003 said:
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
Click to expand...
Click to collapse
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out ?
eminem5055 said:
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out
Click to expand...
Click to collapse
That would be awesome
OK, I ll try to get some permissions before building / posting the revisions.
melodystyle2003 said:
OK, I ll try to get some permissions before building / posting the revisions.
Click to expand...
Click to collapse
Sounds good man! ?
eminem5055 said:
Which dtbo.img did you use as well?
Click to expand...
Click to collapse
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
ha7msterx said:
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
Click to expand...
Click to collapse
ALSO, if the screen refresh part is a placebo, requiring a kernel modification to actually change, then ok.
Embarrassing to state, but I didn't actually test the resultant screen refresh rate, or really anything other than the subjective snappiness of my device.
So now I feel like I rushed to post, but I won't kill the thread because apparently melodystyle2003 is compiling a kernel. Thanks for that.
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Really looking forward to this
melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Freak07 said:
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Click to expand...
Click to collapse
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
melodystyle2003 said:
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
Click to expand...
Click to collapse
It´s not possible to overclock the displays of the pixel 3 or the pixel 3 xl that way. I don´t need to compile a test kernel to be able to tell you.
Displays running in command mode can´t be overclocked that way, unless you have access to internal files or you are able to flash display firmware to your device.
Both panels from Pixel 3 or Pixel 3 XL run in command mode:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L20
https://github.com/freak07/Kirisaku...google/dsi-panel-sw43408-dsc-fhd-cmd.dtsi#L20
Whereas the pocophone runs (as it seems more than one type of display across different units) all used panels in video mode.
https://github.com/d1stru3t0r/testz...qcom/dsi-panel-ebbg-fhd-ft8719-video.dtsi#L24
https://github.com/d1stru3t0r/testz.../dsi-panel-tianma-fhd-nt36672a-video.dtsi#L24
Panels in video mode can be overclocked this way, if it´s desirable is another question.
Sorry to be the bearer of bad news, but it´s simply not possible on Pixel 3 devices.
You can even unpack the dtbo.img, change the line you intend to change and any fps app might show you more than 60fps, but you just fooled the app into thinking our displays refresh at a higher rate than 60fps.