Database Develop

[FAQ] for topogigi's stock GB rom

The original topogigi thread is getting very long. I thought maybe it would be helpful to post some type of FAQ in a separate thread. I will not keep this updated, but I will start the thread by posting the instructions for overclocking with the OC deamon (which is a very frequently asked question in the original thread):
in /etc/andrev_oc you've got 6 files:
- sleep_gov to indicate which governor to use during sleep mode
-wake_gov: same for awake state
-sleep(or wake)_max: max frequency allowed
-sleep(or wake)_min: min frequency allowed.
Open ES File explorer (pre-installed with ROM) and go to settings. Make sure you have [x] Root Explorer and [x] Mount File System
Open etc/andrev_oc as text document, edit the value as you desire and save. A reboot and it's done.
Here are the authorized values:
1408000
1216000
1100000
1015000
800000
503000
389000
216000
Have fun !

Undervolt
To Undervolt _________________________________
Edit 'echo 0,0,0,0,0,0,0,0' UV values via:
volt_scheduler in /system/xbin/volt_scheduler
(i.e. a value of 50, 50, 50, 50, 0, 0, 0, 0 undervolts the top 4 frequencies by 50mV each.)

GPS bug
Don't know if this will work for everyone, but...
Originally Posted by fire3d
i tested this three times now, wipe everything on the phone,
I'am from Germany (if this is relevant for GPS)
install 1.6
do the Setup
install 1.8
enter hidden menu and add the Nokia Supl for GPS
supl.nokia.com
7275
cert = NULL
TLS = on
select nokia and shut down the phone, start it again
After that i get a fix outside nearly instant, indoor it tooks 2-3 sec's,
best GPS ever seen on this Phone.....
Click to expand...
Click to collapse

Found something that could be of help to the ones with gps fix problems like myself in 1.8.
When I start my O2X with GPS off and I set GPS on when phone is booted, I couldn't get a normal fix (just the "1 sec bug")
But I start start my O2X with GPS on, I can get a normal fix.
Maybe this can help Topogigi crush this bug.
Reboot a dozen times with GPS OFF: No Fix, at all or loosing it directly and not coming back
Reboot a dozen times with GPS ON: Fix, and keeps it
I think there's something wrong with initializing GPS when (re)booting with GPS OFF

You describe a method for increasing the voltage, and as it lowered. Than monitoring the current voltage???

I can get the GPS to lock outside it takes a while. The problem is subsequent locks take just as long. So if I go back inside it'll never lock. The GPS on this phone sucks!

http://forum.xda-developers.com/showpost.php?p=18146527&postcount=2126
FAQ by Topogigi, its in the ROM thread.

[Q] Problems with touchscreen

hello
after a year of great health, my nook began having problems with the touchscreen.
first, it began with some phantom touches, but its frequency quickly increased until it reached the point of making it totally nonresponsive.
here is a video of my nook to show how bad this is
http://youtu.be/nnDSP__GEhc
- tried cleaning the screen, and nothing
- tried the ADB method to recalibrate the screen, once it worked for a couple of days and happened again. so i tried to recalibrate again without success
- i have a screen protector since day one
- tried restoring and old nandroid (with clockworkmod), nothing
- upgraded CM7 to the latest version: 242, nothing
after recalibrating i issue a dmesg to the shell and i get the following messages:
Code:
<4>max8903_charger_enable: B&N USB CHARGER(500mA) Detected!
<4>MAX8903: Charging is now enabled!
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TAP1 [2]
<6>kxtf9 1-000f: IRQ TAP1 [8]
<6>kxtf9 1-000f: IRQ TAP2 [1]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [8]
<4>ttsp_forcecal_store: Forcing TP calibration NOW.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Starting Touch panel Calibration: Switch to System Information mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Touch Panel is now in System Information Mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Touch Panel Calibration was successful.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Returning to Operational mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Initializing Gesture Setup.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Power state is ACTIVE
<6>kxtf9 1-000f: IRQ TAP2 [1]
<6>kxtf9 1-000f: IRQ TAP2 [20]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [8]
<6>kxtf9 1-000f: IRQ TAP1 [1]
which seems to show that the touches are still happening
then, in clockwork recovery, i hit the key test option, and it continually shows keysrokes with codes 103 and 108 (even when i'm not touching anything) is this normal??????
so, the question is.... does anyone have an idea that i could try??? should i begin searching for a replacement ?

........ and FWIW, today i tried creating a bootable SDcard using verygreen's image.
booted and the touchscreen was responding fine. so, i booted again from the emmc, and now it seems to be working again....... does this have any sense????????
if the solution persists, i'll update this thread as solved

and the problem happened again..... i think i lost it

Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.

Remove the charger.
Sent from my PC36100 using Tapatalk

selection16 said:
Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.
Click to expand...
Click to collapse
mmm, worth a try, when i get home i'll try that
jerrykur said:
Remove the charger.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
all described behavior is when disconnected from the charger

don_ernesto said:
all described behavior is when disconnected from the charger
Click to expand...
Click to collapse
ignore this

selection16 said:
Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.
Click to expand...
Click to collapse
i tried this, and didnt work, thank you anyways for the idea.....
BTW, i had never used the nook without a screen protector.... it looks gorgeous!!! if this would work again, i doubt i'll put the protector back

I'm curious......is it OVERCLOCKED?
If so, set it back to normal and try it. I'm seeing some strange things when I overclock.

rampart51 said:
I'm curious......is it OVERCLOCKED?
If so, set it back to normal and try it. I'm seeing some strange things when I overclock.
Click to expand...
Click to collapse
it is not overclocked.... but thanks for the suggestion
i think the next step is to hit it with a hammer and see what happens

Dude I've had the phantom touches on both of my nooks. I've had he problem on stock no root cm7 stock rooted, and and currently on miui. It's not as bad on my second nook but it still happens once in a while.
Sent from my NookColor using Tapatalk

[Mini2] Random reboots , crashes and battery drain - anyone else ?

Hello everyone!
I recently started having some rather strange issuses with my phone . This started about 2 weeks ago if I can recall .
First of all , you can find my entire setup in the signature .
Secondly , this happenned about 2 days before I flashed TheWhisp's TWRP . Before that I had my ordinary setup that I've been using for like 6 months .
Now , the first problem I ran into is that the phone seems to freeze for no reason out of the blue . I just left it locked , and when I tried to unlock it some hours later , the status bar was gone , the lockscreen could be interacted with and unlocked , but the launcher and all the interface was frozen . I could bring up the recent apps view by holding down the Home button , so I tried opening Samsung's task manager , but after tapping on the button , the phone was still frozen and no task manager was shown .
A wierd thing about this is that I'd been getting crashes for like every 6h 2 weeks ago , but starting 1 week ago , I've been getting them for like every 12h or sometimes even more .
I've tried fixing this in all the ways I can think of - re-flashed Peter's ROM , re-flashed back all the way from stock , changed the recovery back to CWM 5 , none seem to have worked unfortunately .
Another problem I've noticed recently (starting about 2 days ago) is that the battery is draining a lot faster as well . With a setup and usage that a month ago could keep it up for at least 24h , now it barely resists 18h with a less intense usage .
And finally , here's where the "anyone else ?" title part comes in : it may sound crazy , but I have a friend who's also got a Mini 2 , but unlike mine , his is full stock (no root , no custom recovery , he left it right as he bought it) . And the crazy part is that he's having problems with his phone as well! At the same time as I do! We were attending a class last week and my phone got a crash , then I had this random idea that maybe his phone will crash at the same time , since he told me he's been getting crashes too , so I told him to check his phone and voila ! He got one too . The difference between our phones is that he actually gets reboots , whereas my phone freezes completely and doesn't self reboot .
And now for some actually helpful info , here's something that keeps popping up continuously on the logcat , regardless of what I'm doing with the phone - haven't seen this before in none of my logcats before this problem came up :
Code:
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.681000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.781000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.881000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.981000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1393.081000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
I would be very grateful if someone could help me! I'll have to go on a 2-day trip next week and I don't want the phone to die on me when I need it the most xD
Thanks alot guys and have a nice day!

Does this happen on all ROMs ? (including stock and CM)
Wake lock is responsible for when your device is or is not sleeping. For example, when all apps haven't released wake lock, the device won't go into deep sleep. For now, the best you can do is to revert back to everything stock. Don't log in your Google account or any other account, disable sync, leave it completely stock and see if the problem persist. It seems that something is acquiring wake lock on your device. A virus perhaps? It may sound crazy, but it could be due to some files on your sd and/or infected accounts and so on.. Wipe everything, even both storages

I've just flashed back completely to stock , without wiping the internal & external memory , didn't even connect to my Google account , and looks like the alarmManager lines don't appear anymore on the logcat .
I'm going to start re-installing (not restoring) my old stuff onto my phone and logcat after every major change (app install , kernel install etc) to see if and why the problem appears again .
Thanks for the help! It didn't occour to me that it may be a virus . I'm not an app whizz and don't install a lot of new stuff onto my phone , but unfortunately I don't remember whether I had installed anything fishy before this error started popping up .
I'll keep you updated if I manage to find its source .

Update :
Looks like I've managed to get rid of the alarmManager messages . They were caused by an app called AppLock .
HOWEVER that was not the problem . I've installed AppLock just some days ago . It could have been the faster battery drain cause , but not the crashes cause . My phone was frozen after a missed call (didn't have access to the PC so couldn't get a logcat) about 1h ago .
I've now noticed something else on the logcat - graphics related . I've attached an aLogcat ss (still away from my PC) .
One thing I forgot to mention is that video playback has been pretty grumpy . Every half an hour of playback or so , VPlayer would crash and no other player would work without a reboot .

Since no one else seems to have this problem, you could observe hardware failure.

Wipe batery

Wiping battery stats doesn't help. If you're running android 4+ you could try using Greenify (at least for battery drain)

I had this problem with my galaxy mini (not 2) found out I installed a dodgy app, once I uninstalled it problem was gone.

pryerlee said:
I had this problem with my galaxy mini (not 2) found out I installed a dodgy app, once I uninstalled it problem was gone.
Click to expand...
Click to collapse
You're right, sometime app create (for some reason, why?) zombie processes that uses a lot of battery

Okay so I'm still experiencing this problem with my phone . Hopefully this is not a hardware failure , as a full stock reset will fix it . So it is most likely some virus inside some app , which is wierd because I didn't install some dubious app at all . I have been using all these apps for quite some time and I can't seem to figure out which one might cause the problem . I'm thinking of Poweramp / Rocket Player / AppLock , which I've had some fun with lately , and my Poweramp trial expired , but it's been long since that .
Starting Monday , I will have the time to monitor the phone properly and look into the problem as I should have a long time ago . But until then , I want to check one more thing . I've caught this exception being thrown about every 5 seconds after the system had frozen . From the looks of it and from the research I've done , something might be trying to make a purchase (as I said , it might truly be a virus) but since I have no payment method registered with my Google account , it can't make that purchase , thus throwing an exception . Or maybe it over-flooded some service with requests , which crashed , taking some vital part in the Android workflow down with it , thus causing the freezes .
Here's the exception . If anyone knows whether it is related to some known virus , please let me know .
Code:
W/ActivityManager( 198): Failure sending broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }
W/ActivityManager( 198): android.os.DeadObjectException
W/ActivityManager( 198): at android.os.BinderProxy.transact(Native Method)
W/ActivityManager( 198): at android.app.ApplicationThreadProxy.scheduleRegisteredReceiver(ApplicationThreadNative.java:761)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.performReceiveLocked(ActivityManagerService.java:10857)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.deliverToRegisteredReceiverLocked(ActivityManagerService.java:10922)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.processNextBroadcast(ActivityManagerService.java:10979)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.access$100(ActivityManagerService.java:143)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService$2.handleMessage(ActivityManagerService.java:1082)
W/ActivityManager( 198): at android.os.Handler.dispatchMessage(Handler.java:99)
W/ActivityManager( 198): at android.os.Looper.loop(Looper.java:130)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1337)
W/ActivityManager( 198): Unattached app died before broadcast acknowledged, skipping

Full wipe internal and external storage (i don't recommend you backup the data) install Stock ROM with stock recovery too not the cwm. And then don't install apps that are not popular or any app that you don't find in google play
Sent from my GT-S5570 using xda app-developers app

just go back to stock that what i did and that's ut everything working fine ^^

[Q] Sensors not working in 5.1

I recently updated my Nexus 6 to 5.1 and while using the camera I noticed it wasn't rotating the controls with the phone. I did some further testing and realized that auto-rotate wasn't working either; I tried toggling the setting, but it still didn't work. Doing a factory reset and re-flashing 5.1 also did nothing. I finally tried flashing 5.0.1, and suddenly everything was working, but returning to 5.1 broke everything again. The Accelerometer Monitor app shows no data at all, so it appears the accelerometer is completely dead in 5.1.
Is anyone else having this issue? Is there any way I can fix it besides downgrading to 5.0.1?
I guess that also explains why it seemed like ambient display wasn't activating when I picked up the phone...
Update: Turns out, none of the sensors are working -- accelerometer, compass, light, proximity, etc... the sensor apps in the Play Store say they don't even exist.
Update 2: Sensors are working in the Android M preview.

Accelerometer is still broken in the new LMY47E build. Am I really the only one who has run into this problem? Should I contact Motorola for a new phone?

I have only seen you report the problem. I recall a post long time ago where someone dropped there phone and it got jammed. The smacked it on the corner and it came loose. Not suggesting you do that just telling you what I have seen.

TonikJDK said:
I have only seen you report the problem. I recall a post long time ago where someone dropped there phone and it got jammed. The smacked it on the corner and it came loose. Not suggesting you do that just telling you what I have seen.
Click to expand...
Click to collapse
Hmm, odd. Yeah, I came across that thread while searching for other posts about it. I tried their solution with no luck, sadly. However, as I stated in the first post, the accelerometer works if I flash the 5.0.1 factory image, so I'm pretty sure it's not broken/stuck hardware.

I have this exact problem too. Did you find any solution? I don't want to send my phone to the repair service again...

Floken said:
I have this exact problem too. Did you find any solution? I don't want to send my phone to the repair service again...
Click to expand...
Click to collapse
I still haven't found a solution. I've tried all the 5.1 builds that are available from Google (LMY47D, LMY47E, LMY47I) and the issue exists in all of them. I've considered contacting Motorola to see what they could do for me, but I haven't got a chance to do it yet.

I'm on 5.1 E and it works fine for me..

Maybe one of the 5.1 based custom roms?

For what it's worth, this is what I get in the system log when I try to use an app that uses the accelerometer or other orientation sensors:
Code:
04-01 14:23:40.112 1883 1904 E qti_sensors_hal: processBufferingResp: Result: 1, Error: 5
04-01 14:23:40.112 1883 1904 E qti_sensors_hal: processBufferingResp: 0 Error: 4 Reason: 18
04-01 14:23:40.112 1883 2865 E qti_sensors_hal: enable:sensor(android.sensor.accelerometer) Failed for handle 0 @ samp 50 Hz rpt 0 Hz batched 0
04-01 14:23:40.112 1883 2865 E qti_sensors_hal: Activate the handle 0 is not successful
04-01 14:23:40.112 1883 2865 E SensorService: Error activating sensor 0 (Operation not permitted)
04-01 14:23:40.115 1883 1904 E qti_sensors_hal: processBufferingResp: Result: 1, Error: 5
04-01 14:23:40.115 1883 1904 E qti_sensors_hal: processBufferingResp: 10 Error: 4 Reason: 18
04-01 14:23:40.116 1883 1898 E qti_sensors_hal: enable:sensor(android.sensor.magnetic_field) Failed for handle 10 @ samp 50 Hz rpt 0 Hz batched 0
04-01 14:23:40.116 1883 1898 E qti_sensors_hal: Activate the handle 10 is not successful
04-01 14:23:40.116 1883 1898 E SensorService: Error activating sensor 10 (Operation not permitted)
Floken said:
Maybe one of the 5.1 based custom roms?
Click to expand...
Click to collapse
I think I'll try one of those when I get a chance and see if it's fixed there.
Edit: It doesn't work in the latest Chroma ROM at least (LMY47I based)

Interestingly, the sensors seem to be working again in the preview version of Android M...

[Q] I/ART Starting a blocking GC xposed

Does anyone knows why my logcat has repeating
Code:
I/ART Starting a blocking GC xposed
in logcat? It repeats itself for 10-20 times every few seconds.
Everything works okay though, but I couldn't help feeling that the phone could perform better if I eliminate subtle issues.
I am using Xposed 89 on Nougat (HTC M9/arm64 using ViperROM).