Database Users

[UPD][Tracking] Andriod HD2 Open Issues

Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.

Hi depakjan, This is great, thanks for tracking these issues.

can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.

i think the bsod is fixed with 2.12 radio and above..

Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...

depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem

Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..

Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.

Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.

Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.

badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).

Led Notification is not functioning, especially on Sense build.

backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen

jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2

hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!

Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.

Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy

Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto

I can't unlock the screen with Gingerbread

I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)

r0uzic said:
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
Click to expand...
Click to collapse
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.

Rod3 said:
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Click to expand...
Click to collapse
Thanks, in a couple of hours notice if I have failed the stock rom

I just tried the stock rom GRI40 and I was not locked, so I guess it will be the kernel in CM7.

Not having that problem at all on stock GRI40; by the way, i'm having an odd issue with GRI40 & Gingerbread. The time to auto-lock the screen uses to change by itself; i think it's on 2' by default, but i changed it to 30' on screen settings and also on Widgetlocker settings...well, once a day, the time changes to 2' again. Anybody else having the same issue? Ideas?

Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.

This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.

Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One

Know-Fear said:
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
Click to expand...
Click to collapse
britoso said:
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Click to expand...
Click to collapse
I doubt it is a hardware failure does not happen to me with Eclair, Froyo or Gingerbread stock, just happened with CM7
Buck Shot said:
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Click to expand...
Click to collapse
I don't use trackball wake, but my nexus is completely blocked, even if I press the unlock button, and I wipe everything before to flash CM7

[Q] RoyalGinger 1.3 Issues......

Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.

gitm said:
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
Click to expand...
Click to collapse
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into

I've had the exact same issue when using RC2 with faux's kernel. I've tried the LV and SV versions and still had the same problem.
Finally I gave up and just reinstalled RC2 without faux's kernel and I have not had any issues.
Sent from my HTC Glacier using XDA App

Tazzaras said:
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
Click to expand...
Click to collapse
Yea I have wiped and formated everything. The install I am now on I actually waited a full 30 mins instead of recommended 5 min.Nothing against teamroyal as I have mad respect for what they do, but RoyalGinger has made me a pro at installing it
So far no kernal crashes, which has given me a perma-grin. I'm gonna flash back to the latest LV version of faux kernel (the one that came with it). I'm sure it will be fine as I think the whole problem has to do with the screen off animation. I'll report back with my results.
Update:
It is the screen off animation that is causing my issue. I have flashed the latest kernel and everytime I have the off animation on, it locks. On screen animation works when on by itself, but turn the off animation on, power on and off a couple of times, and it will crash. I'll try to grab the logs and submit them.

Well seems everytime usb debugging is on it simply won't crash, and I can't get emulator to record when the phone crashes. Sorry I can't get a logcat

Same here on my wife's phone. Had to restore a 2.3.2 nandroid because both (CM7 rc2 and RG 1.3) were freezing on wake. Dunno what the cause is because on my mytouch RG 1.3 runs fine since it dropped......

If u read thru the post for Royalginger 1.3 it says that the best kernel for the rom is the kernel that it comes with... it also says u will get best/smoothest response with it set at smartass... I'm not sure if its changed since I've read but give it a try...
Sent from my HTC Glacier using XDA Premium App

So the good news is I was able to get a logcat. I didn't realize that when the phone completely freezes (power on/off does nothing) you can still dump the logcat, hooooray for me. So here is my logcat file, and for the record this ONLY happens when I have the off and on screen animations enabled in the "CyanogenMod settings", with them off I can power on and off without the phone crashing.
[ROM] - RoyalGinger 1.3
[Kernel] - version 2.1.0 Low Voltage
[CPU Frequency] 245~1113
[Governor] Smartass
[Theme] - Honeybread (CM7 honeycomb theme)
[Live Wallpaper] - None

Update:
I did what was instructed in the dev section for flashing the latest Faux Kernel (2.1.2.1). I wiped the cache and delvikcache. I then fixed permissions and installed the kernel. Once the phone got to the lock screen, I waited 15 minutes for the kernel to "settle", immediately rebooted and let it sit for another 15 minutes.
Once that was I done, I enabled both the on and off screen animations, and after power on and off about 20 times, it crashed the phone again. So I am still having the same issue. Also as a heads up, I tried different themes just incase it was the theme, but that made no difference. So I reverted back to screen on/off animations as all off, and still no lockups. I have attached another logcat file, just incase there is some new data in it.
On another note, there simply isn't any last_kmsg file, so I'm sorry I can get you folks the file. It isn't on the phone when it crashes or even when the phone works correctly.

Have you done anything with spare parts?

Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.

gitm said:
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
Click to expand...
Click to collapse
gitm - 1.3.1 should be out by tonight, barring anything weird coming up last minute in testing
and this has the new 2.1.2.1 faux kernel built in but if you want to try in the mean time - go to his thread and flash that kernel (wipe both caches and fix permissions, then flash kernel, then settle for 5 mins on initial boot, reboot, settle another 5 min, then go)
can't remember, are you using stock launcher or a 3rd party?

Using launcher pro.
As for the new kernel, it is still causing the same issue. In my logcats, it says "cpu pegged", and that is pretty odd. Hopefully 1.3.1 will fix it, but I will keep testing and keep you posted

ICS Passion v10

Awesome ROM! I don't have enough posts yet (long time reader, I hardly ever post...) to post in the official thread....so I thought I'd post one here.
Passion v10 (BETA) has been one of the best custom ROMS i've flashed. This only comes (a very very close second) to Simply Honey. I'm sure v11 will surpass it though.
Yeah! ICS on my Vibrant....lovely!

Camera - works whith lag
Bear with balalaika From Russia

I tried v9.2, and it had some definite issues. I went back to Bionix. Then I flashed ICS Passion v10, and it's great for a lot of functions, but it rebooted twice when I received a phone call and tried to call...this is while I was travelling, so I wasn't too happy.
Hopefully all the bugs will iron out soon. I do like ICS.

GPS Lock issue
I just upgraded my t-mobile vibrant to Passion 10.6 and the GPS works but sometimes it doesn't. I'm experimenting with it to figure out the problem.
I found at least one case that if the GPS doesn't work enabling/disabling the GPS didnt see to fix the problem. I rebooted the phone with GPS enabled and then it locked immediately when the phone booted up.

dancer810 said:
Camera - works whith lag
Bear with balalaika From Russia
Click to expand...
Click to collapse
Don't know if you're using GPS Test or NBAngryGPS to test but for hahas I just used GPS without running/fiddling with those two apps and only using the Maps app and GPS works anytime.
Just my observation.
_________________________
SGH-T959 ICS Passion 10.6 (using stock, not Eugenes' kernel)
Working FFC

I'm also in the same boat I am always reading and never posting. Well I need to be able to post now. I'm running 10.6 and all is well I get GPS as good or better then I ever did and my phone is so much faster.
Sent from my SGH-T959 using XDA App

I'm running 10.5 and it works great. I don't use GPS so I don't know if it works well. But I bought a bigger battery just so I could enjoy it for the whole day without any battery drain. Can't wait for v11.
ics passion v10.5
18000mah battery

My previous rom was froyo and it didnt lock as quickly at ICS Passion 10.6. I was quite impressed actually at how quickly it found 11 satellites and locked on to 8-10 of the in use. In a matter of seconds ICS Passion locked on via a fresh boot of the phone.
I always used GPS test on froyo and ICS Passion 10.6 and it worked fine. I even use google maps and it works too. On boot up of the phone ICS Passion 10.6 works worked beautifully.
If the phone sits idle for a while maybe 30 minutes or so and you try gpstest or google maps it never finds a single satellite. I have to reboot the phone in order to get it to find and lock on.
I don't know if any of you have tried that case but that is definitely what is happening on my vibrant. Again with froyo I never had this issue. I could disable the gps and then later enable it and it would lock on after 1-2 minutes with no problem.
I will try a few more things to see if I can isolate it more but its pretty clear at least on my end that it doesn't acquire a lock after being idle for some time.
---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------
I just confirm this. If the vibrant goes into power saving mode where the screen black out after its idle, I can not get a lock on the gps without rebooting the phone.
Both gpstest/google maps and angrygps cant get a single sat

Awesome
ICS Passion v10 is awesome. It's, by far, the best ROM I've ever used... coming from Stock to CM7 to ICS Passion (after a long drought). NeoBuddy89 has resurrected my PASSION for my phone again! Haha... simply awesome.

I'm running v10.6 , no extra mods, running Eugene's v10.6_update kernal and it is so smooth and fast, I don't care about the vibrant GPS, but all else is great, best combo I've found with passion. 2099 score on quadrant with 200-1300mhz and smartassv2.

Yeah running 10.6 Eugene's ed
My only long standing issue with this from as a whole is the low storage message and when I reboot it gets stuck on boot splash finally fixed it with a combination of restore app only in TB with killing fb auto sync and Gmail sync but besides that completely amazing
Sent from my SGH-T959 using XDA Premium App

Sweet!
This ROM is amazing! My only issue is the screen seems to not be as responsive to touch so I have to press a little harder to get things to work. I installed Touch Screen Booster from the market and it seems to be better, still trying different configs. GPS is flawless! Locks in 15 seconds INSIDE my house. I never had that happen on any FROYO ROM.
PASSION for the FTW! This ROM has restored my interest and my faith in my Vibrant, and saved me some $ too. I almost picked up a GS2 last week but held off. I am amazed at how smooth and fluid this ROM is and that my Vibrant is running an OS that is not even available on the GS2 !
Passion 10.6 = Very happy Vibrant owner!

Was using stock 2.2 and it worked fine but I guess that I try out ICS since Samsung won't do ICS for this phone. First I had to flash back to Stock Froyo because Heimdall suite won't work. Rooted the phone, but won't go to clockwork mod. Have to install the rom manager manually then was able to install clockwork mod. After I was able to get into clockwork mod, try to install cm 7.1, but it reboot looping, so I had to pull out the battery and try again and was successful. Then I try to install this ICS, and again, loop reboots and had to re-install again. I guess it is just bad luck of me to try to install ICS.
I try to play some divx movies that worked fine in stock 2.2 but couldn't play the same files in ICS. Anybody know how to fix this? Thanks.

pug_ster said:
Was using stock 2.2 and it worked fine but I guess that I try out ICS since Samsung won't do ICS for this phone. First I had to flash back to Stock Froyo because Heimdall suite won't work. Rooted the phone, but won't go to clockwork mod. Have to install the rom manager manually then was able to install clockwork mod. After I was able to get into clockwork mod, try to install cm 7.1, but it reboot looping, so I had to pull out the battery and try again and was successful. Then I try to install this ICS, and again, loop reboots and had to re-install again. I guess it is just bad luck of me to try to install ICS.
I try to play some divx movies that worked fine in stock 2.2 but couldn't play the same files in ICS. Anybody know how to fix this? Thanks.
Click to expand...
Click to collapse
What player are you using? Try Mobo player, it's free on the Android market.

iynfynity said:
What player are you using? Try Mobo player, it's free on the Android market.
Click to expand...
Click to collapse
Thanks. BTW, I can't see the contents of the sd card from the phone. It thinks the internal memory is my sd card. Second, how do I configure a lockscreen? Third, how do I configure wifi access after I enable it? And finally, how do you configure and resize a widget?

pug_ster said:
Thanks. BTW, I can't see the contents of the sd card from the phone. It thinks the internal memory is my sd card. Second, how do I configure a lockscreen? Third, how do I configure wifi access after I enable it? And finally, how do you configure and resize a widget?
Click to expand...
Click to collapse
Which ICS are you using?
1. Let the moboplayer scan the folder "emmc". It's in the very root of your phone
2. Not all roms have a built in option for this, again, which ICS rom are you using? So if the rom you're using doesn't have it the only way is to use a 3rd party app(not sure if we have this kind of app in the market.)
3. Settings / Wireless & network / wifi settings
4. hold the widget for a few seconds while it's still on the homescreen, there you can resize your widgets.

iynfynity said:
Which ICS are you using?
1. Let the moboplayer scan the folder "emmc". It's in the very root of your phone
2. Not all roms have a built in option for this, again, which ICS rom are you using? So if the rom you're using doesn't have it the only way is to use a 3rd party app(not sure if we have this kind of app in the market.)
3. Settings / Wireless & network / wifi settings
4. hold the widget for a few seconds while it's still on the homescreen, there you can resize your widgets.
Click to expand...
Click to collapse
Thanks. I am using this ICS Passion rom 10.6. Downloaded moboplayer and it seems to work. I am trying to find the lockscreen using the 9 dot swiping unlock screen, but I don't know where to download it. I managed to figure the wifi settings.
The main question about the widgets is that I am trying to add another custom widget where I can add and remove whatever button (cm7 like) but I can't do it. Thanks.

[GUIDE]Jelly Bean on 8013

I have put this all together on the uk release and put it out as a rom here:
http://forum.xda-developers.com/showthread.php?p=34971303#post34971303
So here is a thread to talk about getting the German release of Jelly Bean on the 8013 and the 8010
I cross referenced the way that pimpmaneaton did his redemption rom, being able to work on the 8013 and 8000 with the aroma installer, checked what was different between the two for ICS.
With the build.prop, it was mostly just some changes to from 8000 to 8013 in the naming of things, but there were also a couple things coded out to get it better on the 8013
We have been looking into the dialer commands to see if any will disable the radio, more on post 11 for that testing.
I have had success with no reboots as well as removing the pesky no signal icon. I have included a flashable zip file that will take care of the build.prop, delete the files we know are not needed, disable the telephone by replacing the framework-res, adding in darkman-rs circle 1% battery mod, removing the null signal and airplane mode icons by replacing the systemui.apk
Step one: Download a jelly bean rom
I have been using darkman_rs version of the JB since it is stock and works nicely, also he has a lot of other nice stuff for it like a circle battery mod I like, and the telephony disabler.
Here is a link to his rom http://forum.xda-developers.com/showthread.php?t=1909950
***
Flash rom, clear cache/dalvik
Reboot, login/setup/etc until you reach a fully installed state.
Then reboot to recovery and install the fix zip.
Set cpu to ondemand
***
fix zip for 8013:
https://www.dropbox.com/s/xkb3spitb5vhlas/Complete_jb80xx_v2.zip
fix zip for 8010:
http://db.tt/tNMC0ZAv
The only difference between the two is the device name in the build.prop
-------------------------------------------------
Other fun stuff:
Adding in the 4 way reboot
I got this from Team Unions ROM here http://forum.xda-developers.com/showthread.php?t=1995700
It is a great rom and all the stuff here should work for that rom as well
https://www.dropbox.com/s/v97fqjyuvjkx7f2/reboot2.zip
there are a lot of nice tweaks from pimp my rom
here http://www.xda-developers.com/android/pimp-my-rom-install-tweaks-on-any-android-device/
Set your governor to ondemand has gotten a lot of good reports for stopping the reboots. This can be done with several tools from the market, I use rom toolbox pro, others use setcpu.
This was posted by darksabre_x
Here's SetCPU. It's been released free for XDA members. Donate when you are able.
http://forum.xda-developers.com/showthread.php?t=505419
Also check out this thread for more multiwindow apps and how to add more!!
http://forum.xda-developers.com/showthread.php?t=1985240
Super cool!!
I found this, some more information on the Pegasusq Governor
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
I removed the non flashable zips because a lot of people were getting confused, all the same stuff is in the fix zips above and will be easier to update if need be.
If there are any more things, add them, lets see if we can get this up and running perfectly before samsung does!
Thanks to everyone here for working together to get this running on the 8013!

what do you think is causes the reboots?

TramainM said:
what do you think is causes the reboots?
Click to expand...
Click to collapse
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.

smaw51 said:
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.
Click to expand...
Click to collapse
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it

TramainM said:
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it
Click to expand...
Click to collapse
Yes, I would imagine that would cause damage to a few things. There is a screen dimmer that keeps the screen *on* but has it dimmed to it appears to be off. I don't know what kind of long term effects it would have on the screen would be, because it is still on and has a slight glow to it.
http://www.xda-developers.com/andro...-screen-with-screen-standby-xda-developer-tv/
It is used for things like hooking up to your tv or computer to run things without having the screen on as well. I don't know if that will work or not.
I didn't have any luck changing my csc stuff, but I did have luck with ROM tool box finally freezing apps I wanted to, so well see how that plays out.

Cheers Smaw51 used your buldprop and systemUI giving it another go hopefully the reboot will stop anyway thanks

Try this in the Dialer ##4636*##

TramainM said:
Try this in the Dialer ##4636*##
Click to expand...
Click to collapse
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.

smaw51 said:
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.
Click to expand...
Click to collapse
Friend who dev'd for HTC amaze gave it to me completely turns off the radio

TramainM said:
Friend who dev'd for HTC amaze gave it to me completely turns off the radio
Click to expand...
Click to collapse
How do you know if it works or not? I am still getting power off during charge. After code was put in, it just wiped clean the dialer. Other codes I found I tested on my phone and tablet for various things all brought up a different screen thing.

Here are some codes I found here http://forum.xda-developers.com/showthread.php?t=1894102
*#197328640# Service Mode
*#7353# Self Test (Menu of 12 tests to use)
*#12580*369# --- Main Version (AP, CP, CSC, RF cal, HW Rev)
*#0*# another test
*#0011# service mode
*#0283# --- Loopback Test
*#232338# --- WlanMacAddress (Enable/Disable WiFi Powersave Mode)
*#197328640# --- Service Mode (Debugging, Testing. Use menu > back to go back in menus)
These look more promising:
*#7284# --- Phone Utility (USB Settings) I set both to PDA, didnt really seem to fix anything
*#9900# sysdump, has a few different things you can get for diagnosis stuff

Ill contact him to see if I can get the right one

It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2

pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I believe it is kernel related, but the problem is we did not have the 4.1 kernel source code

pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was thinking it was Kernel Panics when it tried to sleep.

What's odd (in my experience with both JellyNote and the German JB) is that it doesn't happen at a specific period after the device goes idle. Once it happened 2-3 minutes later, other times my Note sat there running fine for an hour or more before suddenly rebooting. I tried both using the ROM as normal, as well as once doing a complete wipe and re-install (of JellyNote) and not installing any additional software or tweaking settings beyond the startup wizard. Didn't seem to matter, I still got reboots at random intervals while idle.
It'd be nice if Samsung rolls out an N801X rom next.

TramainM said:
I was thinking it was Kernel Panics when it tried to sleep.
Click to expand...
Click to collapse
In the v6 supercharger script there is an option to stop kernel panics and keep it from rebooting. Maybe this is the solution.
Sent from my GT-N8013 using Tapatalk 2

Have you tried it?
Sent from my Galaxy Nexus using xda app-developers app

I have put this version of Jelly Bean on my N8010.
To start with I had a couple of reboots when the tab was idle. What I have subsequently done is:
Frozen com.sec.phone 1.0
Frozen Phone 4.1.1 - N8000XXBLJ9
In settings turned Blocking Mode on
I used Titanium Backup to freeze the programs. So far after a reboot I have not had any further reboots on idle - touch wood
Ok, I am not totally sure which of my changes or combination thereof has done the trick. Am afraid I am too impatient to use the new Jelly Bean to determine absolutely.
What I will say from my experience so far is the the tab is much faster than on ICS and stable for me to use all the time. So this seems a very good temporary solution until the offical N8010/N8013 roms come along.

Using Ondemand governor in a N8010 an the moment no reboots...it seems that the problem is the pegasusq governor