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
Related
Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything.
Google Ion 1.6 for HTC Hero.
This project aims at getting the stock Google Ion Rom to run on HTC Hero. No Rosie or any HTC apps will be ever added to that rom. Once fully functional it could be used as a base for cookers.
Current release: Lox-ION-1.0b3 (logcat)
What works:
- place, receive calls
- wifi
- Market
- GPRS
What does not do far
- bluetooth (logcat seems it is relative to libc.so - Uncompatible with current kernel ?)
- trackball
- compass & accelerometer (with akmd > logcat - with ak8973 > logcat )
- GPS
- camera
Note: devs please test hack and share if you fix anything or have any idea
Great! I hope the rest will be fixed soon!
I second that!
Great to hear it.
are you working on the hardware that doesn't work? and whats the progress.
you forgot to mention that the camera doesnt work aswell
Just flashed it, gonna see what I can get working(if anything).
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
J-Zeus said:
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
Click to expand...
Click to collapse
yes you can
I dont know how gecka feels but could we try and keep this thread informative
Just did a bit of snooping around and the GPS does work, you sure you checked it right? I did a bit of tinkering but none of it was related to the GPS at all. Trackball I'm still not sure about, the keylayouts have the same keycodes but still doesn't seem to want to work. Accelerometer just needs the permission to be granted to execute, except I'm not to sure how to do that cause I'm a bit new to linux. As for the bluetooth, don't get me started, its giving me a headache lol xD
hey i m using this rom and its working beautiful...man nice job and the trackball blinks when a phone is ringing ....but doesnt blind at the time of reminders....but still great job...
What about headphone detection? I know with the other Ion ROMs, when you plugged in headphones, it went unnoticed unless you downloaded an app to manually switch the audio over.
For devs only!
Hi guys,
Please, consider the [DEV] in the subject: this thread is for devs only.
If you don't give any fix, just follow the thread by subscribing to it and don't polute it! Thanks.
For now this build is buggy, you'll certainly find more and more bugs, witch I don't care for now as I want main functionality to work first (bluetooth, gps etc...)
robertosandros said:
Just did a bit of snooping around and the GPS does work, you sure you checked it right?
Click to expand...
Click to collapse
Please read carrefully before posting. GPS in in the "not working" list....
robertosandros said:
Accelerometer just needs the permission to be granted to execute
Click to expand...
Click to collapse
Right! Wrong permissions on witch file ???
Good work gecka,
I'm downloading to have a lookie and install now, see if I can have a go at the trackball.
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
kwiksand said:
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
Click to expand...
Click to collapse
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
gecka said:
Please read carrefully before posting. GPS in in the "not working" list....
Right! Wrong permissions on witch file ???
Click to expand...
Click to collapse
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
robertosandros said:
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
Click to expand...
Click to collapse
You sure the phone is not locating you based just on nearby cell towers?
gecka said:
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
Click to expand...
Click to collapse
i dount known if this works but maybe, behnaam haw gotten Accelerometer (Screen rotation) Fixed!
http://forum.xda-developers.com/showthread.php?t=563772
haw u triad hes files? maybe works and maybe u using different kernel ver
Market Apps
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
craig0r said:
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
Click to expand...
Click to collapse
whats your build.prop?
Hi, I noob on this of an Android Phone, I have a HTC TOUCH PRO 2, RHOD210.
I install the FROYO X 2011.01.12 and i put the kernel that have the packet than run the camera and this is OK.
My problem is that the wifi interface is not workink, i am try a lot of solutions that found in this forum, but nothing is ok for me, i change the rootfs like suggest in a forum, modify the wifi-nvram.txt and put the mac address of the wifi, i update the kernel to Latest Kernel Commit# 1253, and i have the same problem.
could someone tell me how to solve the wifi of my rhod210?
Please, I do not want to use windows mobile
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
arrrghhh said:
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
Click to expand...
Click to collapse
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
kleper said:
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
Click to expand...
Click to collapse
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
arrrghhh said:
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
Click to expand...
Click to collapse
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
kleper said:
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
Click to expand...
Click to collapse
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Also, I'm not sure what you mean "slow with this kernel" - by vanilla FRX03 build, I mean the complete bundle - not just the kernel. Plus, kernels are not tied to system images... So I'm not sure what you mean.
arrrghhh said:
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Click to expand...
Click to collapse
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
kleper said:
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
Click to expand...
Click to collapse
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
arrrghhh said:
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
Click to expand...
Click to collapse
I do that, and don't work for me.
Thanks
kleper said:
I do that, and don't work for me.
Click to expand...
Click to collapse
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
arrrghhh said:
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
Click to expand...
Click to collapse
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
kleper said:
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
Click to expand...
Click to collapse
Sticker underneath the battery - not on the battery itself. It's usually in tiny gray font.
kleper said:
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
Click to expand...
Click to collapse
Well, I'd format with the HP tool. (Full format, FAT32) Download this bundle as well.
[SOLVED]
Thank you very much to everyone who answered me and all the developers of this project so interesting, yesterday succeeded in solving the problems I had, my SD formatting, reinstalling Froyo x version 2011.01.12 and puts a kernel of the chamber, after That did the trick again wifi-nvram.txt file, according to the link that let me arrrghhh one of the threads of this forum, after that the WIFI has started to work wonders.
Then my HTC Touch Pro 2, RHOD210 remain with:
WIFI
CAMERA
GPS
PHONE, DATA AND YOU
AUDIO
Thank you very much.
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
eu0741924381 said:
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
Click to expand...
Click to collapse
WEP actually seems to work on mine. Strange as that is.
Other problems
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
kleper said:
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
Click to expand...
Click to collapse
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
jchutch2 said:
WEP actually seems to work on mine. Strange as that is.
Click to expand...
Click to collapse
WEP should never, ever be used in any circumstances if it can be avoided. That protocol is extremely insecure...
arrrghhh said:
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
Click to expand...
Click to collapse
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
kleper said:
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
Click to expand...
Click to collapse
Well, I'd recommend 1250 then I guess... Usually I recommend the newest GIT kernel, which is currently 1253.
FYI, you already can remove Windows and flash the device to run Android natively. It's just not as stable as haret, but it's getting there. Plus, it's only a partial NAND boot - only init and the zImage are actually loaded on the MTD if I'm not mistaken, everything else is on the SD card (which is still 99% of the data...)
But, if you're feeling brave and really do want to completely get rid of WinMo, NAND boot away... can't say I didn't warn ya
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveats:
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
BT might still be flaky
The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
logcat attached
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
welard said:
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
Click to expand...
Click to collapse
Interesting, does any sound work...? Does it play thru the earpiece instead of the rear speaker? What about previewing ringtones? Next time you pull a logcat, make sure to use -v time. Using GetLogs makes it much easier .
Thanks for testing btw. The more the merrier! If we're going to make this change global, we want to make sure no devices are left in the dust. So it's up to you guys to test and ensure that it works properly! If it doesn't, we'll try to fix it.
If anyone feels like hopping on #xdandroid on freenode while testing, that would be great! Thanks again!
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
am20033 said:
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
Those commands are necessary if you have a SD card that doesn't play nicely. If you need 'em, put 'em in.
Thanks for the logs, I'll pass them on. Anything you can say about 'em? What happened during the logs...? Please be as specific as possible. The more information, the better.
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
arrrghhh said:
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
Click to expand...
Click to collapse
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
welard said:
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
Click to expand...
Click to collapse
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
arrrghhh said:
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
Click to expand...
Click to collapse
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
welard said:
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
Click to expand...
Click to collapse
Post those CSV's if you could!
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
hear are my csv's......thanks...
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
cbolumar said:
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
Click to expand...
Click to collapse
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
arrrghhh said:
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
Click to expand...
Click to collapse
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
cbolumar said:
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
Click to expand...
Click to collapse
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
arrrghhh said:
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
Click to expand...
Click to collapse
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
cbolumar said:
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
Click to expand...
Click to collapse
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
arrrghhh said:
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
Click to expand...
Click to collapse
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
cbolumar said:
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
Click to expand...
Click to collapse
Don't misconstrue, I haven't done any of the actual development on this acoustic code .
See Jerome's tree if you want to see where this all started. A few others have cloned his tree and made some modifications. We're still working out the kinks. Perhaps it can help your port as well...
Like I said earlier, I am betting the userland stuff will work for you folks without a ton of changes (don't know for sure!). The kernel stuff for this new acoustic will need to be ported - our kernel will not work on your device.
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?
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