Develop Bugs

[Q] Jagged/Low Res Display - Multiple ROMS

Hey everyone! Thanks in advance for helping.
I've been running a CM9 nightly from Dec 23rd for a while now, being too busy to change.
Yesterday, I backed up everything and did a full reset (factory, cache, dalvik) and flashed the latest LiquidSmooth ROM and the gapps package they have in the thread. Restarting the first time, the liquidsmooth logo just kept going during boot and never sent me into the OS, which isn't unheard of, so I just held the power and hoped nothing bad happened. On the next reboot, everything was fine.
Here's where the problem started: The little curves and detailing on everything, from the type to the app icons to any image, all looked jagged! The battery indicator circle in particular looked terrible. Now mind you, everything worked fine and was entirely usable, but the fine edges just cut into my eyes.
So, I reset everything again, and glashed the latest CM10.1 Wild in the Night. Same exact look! Sorry I don't have images, but I took screenshots and I ran into another problem with the media process freaking out on the ROM.
Here's the kicker: I restored my CWM backup, and CM9 looks perfect. Maybe it's AA or something? Not sure. Any tips? Thanks!

Flash back to stock and see if that fixes it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Its a CM10.1 kernel issue. So it will affect roms that use the same kernel, which is everything AOSP 4.2.
TW jellybean, or anything ICS or older will not have the issue.

Adreaver said:
Its a CM10.1 kernel issue. So it will affect roms that use the same kernel, which is everything AOSP 4.2.
TW jellybean, or anything ICS or older will not have the issue.
Click to expand...
Click to collapse
Ah, so everyone else on AOSP 4.2 is having the same issue? Or is it just a known bug that some encounter? If that's the case then I guess I just find the best JB ROM for now.
The odd thing is thta I've googled around with multiple keywords and no one else has mentioned it, although I may be using the wrong terms.

Fencefry said:
Ah, so everyone else on AOSP 4.2 is having the same issue? Or is it just a known bug that some encounter? If that's the case then I guess I just find the best JB ROM for now.
The odd thing is thta I've googled around with multiple keywords and no one else has mentioned it, although I may be using the wrong terms.
Click to expand...
Click to collapse
I'm not seeing this issue on the newest pacman from a few hours ago. I imagine other aosp ROMs will soon follow.
Sent from my Epic 4g Touch on PACman

[Q] Rooting problems

Hello i've some problem with my T-Mobile Galaxy Note 2.
Last week i updated my phone on Android 4.3 version.
Unfortunelly i had a wifi bug and I couldn't connect to internet, so I decided to downgrade it to 4.1.2. I've flashed my stock ROM with the newest one. (thanks to this link http://forum.xda-developers.com/showthread.php?t=2102380 )
Afterward, i would rooting my phone and install custom binary CWM by this thread, option 2.
However i can't modifiy system files. I consequently would verify my status root by Titanium Backup. And that's really strange because it is already rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...
​
So i'd like to know how to resolve my problem, i how to modify system files?
(PS: sorry for my bad English!)
PS2: That's the same thing if i connect it on SSH/FTP protocols, unable to modify too.

I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.

DLinkwit said:
I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.
Click to expand...
Click to collapse
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?

Zebra_Cat said:
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?
Click to expand...
Click to collapse
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.

DLinkwit said:
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.
Click to expand...
Click to collapse
I didin't understood that happened to me,
After several minutes and after downloading an alternative file explorer, SU granted to me to modify system files.

[Q] GB27 update help

currently trying to update to jellybean using rwilco12's method it is currently on factory.img and hasn't progressed any further. It's been there for about 20 minutes and the status bar hasn't moved on my device or my PC. am i screwed?

gmc2jz said:
currently trying to update to jellybean using rwilco12's method it is currently on factory.img and hasn't progressed any further. It's been there for about 20 minutes and the status bar hasn't moved on my device or my PC. am i screwed?
Click to expand...
Click to collapse
Would you be able to provide some additional info? What build were you previously on, have you had issues in the past, etc.
Thanks!

i was on 4.0.4 ics tried using kies to update but kies ides everytime i try so i tried a oneclick method but when i got to factroyfs.img the status bar stopped moving at all i ust switched usb cords and ports and restarted the process maybe it will work this time

same results oh and no issues before this but this is the first attempt a rom flashing on this device

rwilco12 said:
Would you be able to provide some additional info? What build were you previously on, have you had issues in the past, etc.
Thanks!
Click to expand...
Click to collapse
how long does it normally take maybe i'm just being impatient?

gmc2jz said:
how long does it normally take maybe i'm just being impatient?
Click to expand...
Click to collapse
It usually takes a good half hour or so for the whole process
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

For future use, NEVER, EVER remove the USB while flashing. Unless you wait at least an hour and nothing happens. Had it been flashing the recovery/bootloader right then you may have bricked your device.
Also, while flashing it may appear to hang. It isn't always the case.

gorei23 said:
For future use, NEVER, EVER remove the USB while flashing. Unless you wait at least an hour and nothing happens. Had it been flashing the recovery/bootloader right then you may have bricked your device.
Also, while flashing it may appear to hang. It isn't always the case.
Click to expand...
Click to collapse
It was hanging with the one click just got it working had to use the battery from my captivate with some modification was a crap phone any way.

Android OS using lots of data

Noticed my Android OS is using almost 1gb of which doesn't seem right.
https://m.imgur.com/p1bAilv,XvmBuaw
Any ideas?

Edit 3: Updating will fix this properly.
Edit 2: That didn't fix it...
Edit: I've seemed to "fix" it. From my reading it is a background service trying to do a seamless update in the background. I disabled "com.qti.service.colorservice" using titanium backup and restore and it seems my background data usage has stopped. No negative consequences so far but it may prevent seamless updates. Another fix would probably be updating to the latest patch version...
Idk but I hope you get an answer... Been killing my battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also seems to hit Wi-Fi...

for me the issue did not go away until I did a factory reset

danw_oz said:
for me the issue did not go away until I did a factory reset
Click to expand...
Click to collapse
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.

jhs39 said:
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
Click to expand...
Click to collapse
It has been a while but I'll reply so anyone else who comes will know. My state before and after was the same. All that changed was my OS version. Flashed the flash-all.sh after removing the -w, flashed the April bootloader (so no boot signing stuff, not the safest or recommended thing), booted TWRP, flashed twrp, flashed supersu, and then rebooted. No other mods besides adaway.

Are you on stock, rooted or unlocked bootloader? I had the same issue on stock (unlocked bootloader) where it was trying download an update repeatedly. I had to actually flash a custom rom to make it stop. Verizon did credit me back for the data it used.
Feel free to read my forum post there and try those steps. - https://community.verizonwireless.com/message/1500910#1500910

Don't ask me how I know but this is a backdoor to access your device. Be careful!

paulJW said:
Don't ask me how I know but this is a backdoor to access your device. Be careful!
Click to expand...
Click to collapse
downloading the security update(s) is a backdoor in?
Riiiight

y2grae said:
downloading the security update(s) is a backdoor in?
Riiiight
Click to expand...
Click to collapse
he said dont ask him how lol

I had to factory reset before this stopped

[QST] - N976B - S-Pen stopped working after rolling back to stock

Hi there,
I have an issue with my S-Pen. it suddenly have stopped working with my device.
I own a N976B Note.
I guess it is an issue with the firmware, because the stylus is recognized on my other devices and the other styluses are not recognized on my note.
To help you understand the history i want to sum up some steps.
1. my phone had a t-obile branding, witch i wanted to remove, so i flashed another csc rom to get rid of that. (back in 2020)
2. After some annoyance by advertisement and the wish to get root and a custom rom, i installed Dr.Ketan Rom and was pretty satisfied, but the hassle with manual updates was a draw back, so i decided to roll back to complete stock to get OTA.
3. After some huslte and some rookie mistakes by trying to install a n975 stock rom on my device, i figured it out and flashed the matching rom. but now the stylus or the digitizer seems to be corrupted. the firmware version is not recognized by the phone. see the screenshot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some attempts to get it running again, i installed the very stock rom for my phone several times. (N976BXXS7FUI1)
I even checked "re-partition" and flashed with the matching pitfile in odin.
But there still no luck.
do you guys have some tips?
big thanks in advance!
greeting

Play with it. Spen's can be ornery as mules, once you get it going you're good.
They don't like being neglected for months.
My stock one was neglected. Took a couple days of playing with and then boom it stated charging like nothing ever happened.
Until it shows it's taking a charge it will do nothing. It will play dead.
Try clearing the system cache, reset network, pray to the pagan gods, play with it more... in and out, etc. Try enabling multiple spens, try disabling same... don't cross your spens, use the one for the 10+
Guess it just needs a good fk to get it going
I have 2 10+'s, both stock* and both run very well. Loading custom roms isn't needed, can kill desirable features and makes troubleshooting** much more difficult. That said if you're back on a stock rom the spen and associated hardware/firmware/software are likely good... it's just showing you who's boss. Play with it at least once a day, it will likely perk up in a week and stop it's wallflower act.
*with a package disabler and heavily optimized. I never update if it's running fast and stable; many apps are still running on their factory load as well. One 10+ is running on Pie, one on Q.
**Do Not enable power management. Make sure you didn't disable a needed parent/dependency apk! Do not ever, ever load Android 11 or higher, the kiss of death. Of course I could be mistaken, but probably not...