Develop Bugs

Jager

Any one tried this.
Im installing it now
http://incredibleroms.com/roms/jager/

I'll give it a try.

Failed on install in Rom Manager.
Reverting to leaked 2.2 now.
Bummer it looked great without sense.

Jager : Update
I got it up and running well. I installed it using ROM Manager, wiped the cache and let it do its thing. Something odd though. I cant seem to get the "Checking phone storage" icon in the status bar to go away. 720p recording, 8mp camera, wireless tether and adw launcher are all included and working. Im going to try to get ahold of the developer, seems like some good work.
-Craig

Edit
Sent from my ADR6300 using XDA App

Its 2.2 through and through. Im giving it another shot and reinstalling it to troubleshoot the "Checking phone storage" error.

also failed for me in rom manager, coming from 2.2 sense leak

SR3TLAW said:
I got it up and running well. I installed it using ROM Manager, wiped the cache and let it do its thing. Something odd though. I cant seem to get the "Checking phone storage" icon in the status bar to go away. 720p recording, 8mp camera, wireless tether and adw launcher are all included and working. Im going to try to get ahold of the developer, seems like some good work.
-Craig
Click to expand...
Click to collapse
Checking on that right now not sure about the rom manager issue will have to check with koush on that... Working on an update now with more fixes and changes...
CJ

CaptainJager said:
Checking on that right now not sure about the rom manager issue will have to check with koush on that... Working on an update now with more fixes and changes...
CJ
Click to expand...
Click to collapse
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out

jgrimberg1979 said:
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out
Click to expand...
Click to collapse
Oh haha didnt know i was responding to the creator of the rom duh/ Anyways while i got you thanks for the rom, i like all of your roms. also right now i have the 2.2.4 version installed but when i go to the site it shows the previous one and not the 2.2.4?

...
Thanks dude. Let me know what the deal is. Also, something to look into, when you answer your phone, the htc sense slide up slide down is appearing, not the slide deal. Looking forward to trying out your work.
-Craig
Is ADW really the way to go, Ive played with Launcher Pro; its pretty bad-ass.

jgrimberg1979 said:
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out
Click to expand...
Click to collapse
I just cant get this installed....followed your steps. Anything else maybe you left out? I tried rom manager already.

santana11981 said:
I just cant get this installed....followed your steps. Anything else maybe you left out? I tried rom manager already.
Click to expand...
Click to collapse
Which version are you using, because i am using 2.2.4 but when i tried the previous one which was 2.2 it didnt work. when i check about 45 mins ago the old one 2.2 was back up and the version i am on 2.2.4 was taken down for some reason. I just checked a second ago and the latest one is back up, so try that one if you havent yet, but dont use rom manager because it doesnt work for some reason and follow the steps that i put up

installed this rom and I had no data connection. Rest the phone and no luck, also did a battery pull and still no data. Did *228 and let it reset after programming and all seems to be working fine. Thanks for a great rom.

jgrimberg1979 said:
Which version are you using, because i am using 2.2.4 but when i tried the previous one which was 2.2 it didnt work. when i check about 45 mins ago the old one 2.2 was back up and the version i am on 2.2.4 was taken down for some reason. I just checked a second ago and the latest one is back up, so try that one if you havent yet, but dont use rom manager because it doesnt work for some reason and follow the steps that i put up
Click to expand...
Click to collapse
I clicked the link in your original post and that still shows 2.2.0....but when i went to main page i see updated version...thanks dude

Wow, I had no idea people would have this much trouble with it. I can post my 2.4 version of it up if anyone wants to give that a try. Hit me up if your interested.

I can post the 2.24 version if anyone is interested.

SR3TLAW said:
I can post the 2.24 version if anyone is interested.
Click to expand...
Click to collapse
its back up now

This is an unusal situation but eventually everyone should be able to get it, like i said it took me a couple of trys. Its deferent than most roms because this on actually forces a full wipe, which is def unusual. Also one thing i noticed when i put it in the cooker just to see the specs and it show "unsecured boot" which is unusal for roms to have

Yea it is back up.
Some bugs I found:
Search feature is not working from home screen.
At first install the messages app doesent seem to be installed correctly and for some reason their is no phone app in the launcher home row.
MMS does not work
couldn't get teh wireless tether in AP mode working

Power button reboots phone with Skyraider 3.3

Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?

patsfan1130 said:
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
Click to expand...
Click to collapse
You sure its Skyraider? That happened to me... Phone wouldnt shut off, if your in dark you can see the screen doesnt even shut down. With me though, it would shut off if plugged in.. Turned out the phone was damaged, a power surge damaged it. Got it replaced. If you flash another rom and it still wont shut down, then your gonna need a replacement.

Thanks for the response Mike. No, It does not happen with any other ROM I flash. Been bouncing between CM, Virtuous and uncommon for a week now and the power button works as it should.
I dunno, I realize I am a n00b with all of this but it simply doesnt make sense to me
Again, Thank you for the response

What radio are you using? A lot of people using 2.05 were having that issue and it went away when they upgraded to a 2.15 radio baseband.

No problem. But what you have going on is very odd, i wasnt aware that a ruu could do that. Try upgrading to the latest radio.

That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28

patsfan1130 said:
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
Click to expand...
Click to collapse
Yes, that's the baseband version and you should be good to go with the one you are using. The only other things I can come up with is to ensure you are S-OFF and running HBOOT 0.79 or higher.

Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.

patsfan1130 said:
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
Click to expand...
Click to collapse
Not a problem. This is how we learn. To find your HBOOT version power down then reboot into recovery. When you get to the white recovery screen look in the top left corner. The first line should state S-OFF and the second line should state your HBOOT version.

I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions

I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.

patsfan1130 said:
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
Click to expand...
Click to collapse
Well that's unfortunate. I read a couple of posts in the Skyraider thread that sounded as though a couple of people had the "recommended" setup (like you) but also had the reboot problem. Those posts seemed to get no response so I guess there was no fix found. Most of the discussion on this problem starts around post #2432 in the Skyraider thread if you want to do some more digging but I couldn't really find anything more.
Some other factors to consider:
When you first flashed the ROM did you wipe all data? (factory reset, wipe data cache, wipe dalvik cache).
If you flashed a custom kernel, try going back to the stock kernel.
What version of ClockworkModRecovery are you running? They released a buggy update a couple of weeks ago and it was pulled shortly after release so if you have a version higher than 2.5.0.5 then you should revert to an older version of CWM.
You could flash the 2.15.00.09.01 radio baseband but I don't think it would make a difference with this problem. Also, if you screw up or accidentally flash the same radio over itself then you will have a brick so use extreme caution if you decide to go that route.
That pretty much exhausts my knowledge on the subject so if everything is as it should be then you could always try wiping everything and flashing the ROM again.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
I didn't think of that but definitely a possibility. Good call.
Best of luck.

RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
Well wouldn't you know it! Problem solved
I did not know the add ons were not compatible
Thanks everyone!

I'm glad I was able to help...
Really though, good to hear you got it working. Enjoy.

$100 reward to anyone that can help w/ Cyanogen

I threw this out on Twitter and at Cyanogen's forums, but I thought I'd give you guys a shot as well as this seems to be the most active forum there is.
I'm absolutely DESPERATE to get cyanogen back on my phone. I had 6.1 RC1 set up perfectly - I tweaked the **** out of my phone - and then I tried to use the camera... no dice. Nothing. Can't use any camera application at all. I always get the same response: Activity Camera (in application Camera) is not responding. I get a black screen, then the option to force close or wait.
I have tried putting on 6.0, 6.1 RC1, and the nightly build... none had a working camera. I flashed everything back to stock, and the camera is working like a charm again... BUT EVERYTHING ELSE SUCKS!!! I can no longer stand stock, thus my offer to pay for help. I just got my phone, and it was new, so I thought maybe the radio version or the HBOOT versions were causing problems. I have:
HBOOT: 2.02.0000
Radio: 2.15.00.09.01
I don't see how either of those would cause a problem with the camera since everything else was running smooth as silk.
Thanks for the great work you all do, and thanks for any help you can give me.

you try flashing any other kernels? try flashing snap's kernel

I used to have that problem, do you have google goggles installed? Or any other apps that may use the camera? Try uninstalling them, then opening up the camera, then you can reinstall them after.

Is your phone hardware revision 0004? If so, you're probably going to have to wait for HTC to release the source code to the kernel from the 3.30 update, because the 0004 models have a new camera which seems to require a new driver. You'll probably have the same issue with the stock ROM if you flash a custom kernel on it.

I had SNAP 7.6 installed, forgot to mention that.

WrlsFanatic said:
I had SNAP 7.6 installed, forgot to mention that.
Click to expand...
Click to collapse
what Ninja said, i remember reading about those 0004's in the general forum

Noxious Ninja said:
Is your phone hardware revision 0004? If so, you're probably going to have to wait for HTC to release the source code to the kernel from the 3.30 update, because the 0004 models have a new camera which seems to require a new driver. You'll probably have the same issue with the stock ROM if you flash a custom kernel on it.
Click to expand...
Click to collapse
This is exactly why. You are SOL for a bit.

apristel said:
This is exactly why. You are SOL for a bit.
Click to expand...
Click to collapse
Actually, it says I have hardware version 0003. Any other way to check my camera version?

WrlsFanatic said:
Actually, it says I have hardware version 0003. Any other way to check my camera version?
Click to expand...
Click to collapse
Maybe try fixing permissions or something..idk. I think its an option in rom manager maybe? I read about ppl talking about it when stuff is broken and they say it helps.
Other than that, try flashing miui to see if that camera works, its based off of CM so if it works, thats always a good sign..if worse comes to worse, you can flash CM6 and then push the camera from MIUI.
From CM6 and 6.1 RC, just try some other kernels, king's, netarchy's or even the new toast .35 kernel.

ms79723 said:
Maybe try fixing permissions or something..idk. I think its an option in rom manager maybe? I read about ppl talking about it when stuff is broken and they say it helps.
Other than that, try flashing miui to see if that camera works, its based off of CM so if it works, thats always a good sign..if worse comes to worse, you can flash CM6 and then push the camera from MIUI.
From CM6 and 6.1 RC, just try some other kernels, king's, netarchy's or even the new toast .35 kernel.
Click to expand...
Click to collapse
OK, I'll try that and let you know how it goes. THANKS!

to run the fix_permissions script open up a terminal emulator and enter
Code:
su
fix_permissions
or with adb just 'adb shell fix_permissions'
Also try wiping the camera apps cache or maybe even cache & dalvik from your recovery.

Had what sounds like the same problem, all i had to do was reboot to fix mine tho and i could recreate the problem by pressing the camera button twice when trying to take a picture, not sure what it was but i had all the same settings as you, i wiped everything flashed a sense rom then wiped everything and flashed back to CM6 6.1 RC1 and everything seems to be fine hope this helps

Try wiping and flashing through Amon RA (if you have been using ROM Manager instead).

Can someone link to some kernels that will be stable with Cyanogen RC1 so that I can try them? Also, just to make sure, I should be able to flash this over top of cyanogen without a problem, right? Of course I'll no a NAND backup, but I'm hoping it will work without that.
Sent from my PC36100 using XDA App

WrlsFanatic said:
Can someone link to some kernels that will be stable with Cyanogen RC1 so that I can try them? Also, just to make sure, I should be able to flash this over top of cyanogen without a problem, right? Of course I'll no a NAND backup, but I'm hoping it will work without that.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
scroll to the bottom. And yep, you can flash them on top of cyanogen without a problem. did you try flashing miui and seeing if that camera worked?

Just tried Kings 2 bfs... No dice. I'll try another tomorrow.
Sent from my PC36100 using XDA App

There have been some reports of people with version 003 having the new camera. So if you bought your phone in the month of November chances are u have the new camera and will have to wait till cyanogen writes drivers for it.

xHausx said:
to run the fix_permissions script open up a terminal emulator and enter
Code:
su
fix_permissions
or with adb just 'adb shell fix_permissions'
Also try wiping the camera apps cache or maybe even cache & dalvik from your recovery.
Click to expand...
Click to collapse
Not knocking your help, I appreciate it, but as stated - and as I figured - I simply will not be able to use my camera until the source code with the new camera drivers comes out. I did try this, and it didn't do anything.
And I can't wipe the camera app cache because I can't even open the application. Click on "Camera", screen goes black, eventually it force closes.

Maxy6 said:
Try wiping and flashing through Amon RA (if you have been using ROM Manager instead).
Click to expand...
Click to collapse
Amon Ra is all I've ever used, so that isn't a problem.
As for the $100, if this really can't be fixed, then I'll just wait until the future Cyanogen release that will include the newer camera drivers and throw in anothere $50 to those guys for all their help. I'm sure it will happen eventually.

WrlsFanatic said:
Amon Ra is all I've ever used, so that isn't a problem.
As for the $100, if this really can't be fixed, then I'll just wait until the future Cyanogen release that will include the newer camera drivers and throw in anothere $50 to those guys for all their help. I'm sure it will happen eventually.
Click to expand...
Click to collapse
Yeah, most of the phone sold in November have the new camera that just doesn't work well with the old kernels out there atm. I'm using Myn Warm 2.2, and the only kernel I can use is the Stock #10 while having the camera work.

Camera and YouTube won't work

Hi all,
I followed this thread (http://forum.xda-developers.com/showthread.php?t=1626895) for returning to stock 4.0.4. All went good, but now my camera and youtube app don't work.
I also installed JB through OTA, but the problem still here.
Now I've followed all the step again, but I have the same problem yet. :/
I read around that it can be related to a wrong build.prop, but my system now is a virgin YAKJU, nothing modified..
What can be the problem? It's an hardware fault??
edit: noone of the camera applications in market work :/
thank you for your help

diaSalvatore said:
Hi all,
I followed this thread (http://forum.xda-developers.com/showthread.php?t=1626895) for returning to stock 4.0.4. All went good, but now my camera and youtube app don't work.
I also installed JB through OTA, but the problem still here.
Now I've followed all the step again, but I have the same problem yet. :/
I read around that it can be related to a wrong build.prop, but my system now is a virgin YAKJU, nothing modified..
What can be the problem? It's an hardware fault??
thank you for your help
Click to expand...
Click to collapse
Ever done a super wipe?

animal24 said:
Ever done a super wipe?
Click to expand...
Click to collapse
What is a super wipe?
I tried to wipe, wipe dalvik cache, and restore factory data with CWM, but without results. Furthermore the method I've followed has already wiped all.
I have to do anything else?

animal24 said:
Ever done a super wipe?
Click to expand...
Click to collapse
I looked for superwipe and I found a script provided by android revolution hd (http://forum.xda-developers.com/showthread.php?t=1361348) I tried it, but still doesn't work.. ://

diaSalvatore said:
I looked for superwipe and I found a script provided by android revolution hd (http://forum.xda-developers.com/showthread.php?t=1361348) I tried it, but still doesn't work.. ://
Click to expand...
Click to collapse
Are you installing apps first? are you sure your doing full factory image for your hardware? another thing I'd try is booting into clockwork without installing it, from boot loader and formatting /system. Then do factory image.

I have a similar problem, where my camera and the google talk app (for some reason) won't work. I posted about this about a week ago, but received no useful responses, which probably means this is an extremely rare problem. Superwipe didn't work for me, so if you haven't done so yet, save yourself some time. I haven't time reverting the phone to stock, and that's about all I haven't tried.

daedalusbound said:
I have a similar problem, where my camera and the google talk app (for some reason) won't work. I posted about this about a week ago, but received no useful responses, which probably means this is an extremely rare problem. Superwipe didn't work for me, so if you haven't done so yet, save yourself some time. I haven't time reverting the phone to stock, and that's about all I haven't tried.
Click to expand...
Click to collapse
I tried almost everything: all kind of wipe (also superwipe), format, CWM (also last one, 6.0.0.5), TWRP, stock yakju from google dev, stock upgrade to JB, some JB rom.. nothing.
Now I'm convinced that is an hardware problem, it happened after a flash (to stock rom), but I think is a coincidence.
GTalk works for me.
Camera doesn't work, it goes in timeout.
Same thing with youtube (app starts, but when I select a video, it doesn't start, maybe youtube launch an intent for check camera availability, or something like).
Also other camera application from market don't work, and so application which use the camera light.
Another strange thing is that some times, when I turn on the phone, it doesn't start on first boot, but it restart once or twice and then boot.
If someone has a good advice, I'm happy to hear.
thank you again :/

having the same problems as u do.

Had similar issue and also couldnt save web images, followed @ickboblikescheese advice from paranoid android thread, use a root explorer to go into system/apps and delete quicksearchbox.apk then download google search from playstore and install. After a reboot i had full functionality of camera etc restored. Dunno if it will work for yas but probably worth a try
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5

buddy, do u mind sharing me the post link

[Q] tablet reboots after going to sleep

Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?

What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.

RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.

Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.

Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA

Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?

There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634

OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?

aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA

pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.

aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA