search

Jasper-1024 / NoWakeLock

An application that controls Android wakelocks can run on Android N and later.
GNU General Public License v3.0
97 stars 8 forks source link

Migrate from Amplify to NoWakeLock #14

Open varunpilankar opened 1 year ago

varunpilankar commented 1 year ago

Hi @Jasper-1024

Is there a way to migrate from Amplify to NoWakeLock? Or do I have to do it manually?

This could be a really good feature to add into the future build.

Also when is your next release coming out? I read you were releasing a update somewhere in December.

Jasper-1024 commented 1 year ago

Now you have to migrate manually. After the first stable release, the migration will be added to the todo list.

In December 2022 China significantly changed its policy, and I am currently suffering from the after-effects of the Omega BF1.7 infection, which makes me easily tired and sleepy, and I had to postpone my plans.

varunpilankar commented 1 year ago

Noted.

Oh, my bad. Hope you get well soon.

Looking forward to your new release. I'm not upgrading to A12, just coz I it doesn't have Amplify like stable module in place. Planning to get on Lineage ride.

Fingers crossed 🤞🏻

varunpilankar commented 1 year ago

@Jasper-1024 hope you are doing well? Just wanted to follow-up on this project.

varunpilankar commented 1 year ago

Hi Jasper,

Last update about NoWakeLock was, you were working on it a stable release soon but due to your health you didn't release it.

So just wanted to follow-up on our conversation and check if you made any progress.

Regards,

Varun

Sent from my mobile device, please embrace the typos.

From: Jasper Hale @.> Sent: Monday, July 24, 2023 3:32:41 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14)

why ？

于 2023年7月24日 UTC 上午9:23:12, Indrasen Pilankar @.***> 写到:

@Jasper-1024 hope you are doing well? Just wanted to follow-up on this project.

-- Reply to this email directly or view it on GitHub: https://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1647540088 You are receiving this because you were mentioned.

Message ID: @.***>

使用 K-9 Mail 发送自我的Android设备。

― Reply to this email directly, view it on GitHubhttps://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1647602888, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UUDYI2I6HQ27K7ZUILXRZB4DANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

Jasper-1024 commented 1 year ago

Hi Jasper, Last update about NoWakeLock was, you were working on it a stable release soon but due to your health you didn't release it. So just wanted to follow-up on our conversation and check if you made any progress. Regards, Varun Sent from my mobile device, please embrace the typos. ____ From: Jasper Hale @.> Sent: Monday, July 24, 2023 3:32:41 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14) why ？ 于 2023年7月24日 UTC 上午9:23:12, Indrasen Pilankar @.> 写到: @Jasper-1024 hope you are doing well? Just wanted to follow-up on this project. -- Reply to this email directly or view it on GitHub: #14 (comment) You are receiving this because you were mentioned. Message ID: @.> -- 使用 K-9 Mail 发送自我的Android设备。 ― Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UUDYI2I6HQ27K7ZUILXRZB4DANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

I'm very sorry, I misread the github notification email and mistakenly thought it was a spam email. This email did not indicate the context.

At present, I have graduated and left school. My work direction is C language development. The time I can devote to nowakleok is very limited. The progress is not great, but unless there are special reasons, I should continue to work on this project.

varunpilankar commented 1 year ago

Noted.

Can I use the current build on Android 10? Is it stable enough to replace my existing Amplify app?

I think migration would be a great challenge for me as I don't even remember which all wakelock I have limited until now. 🙈

Regards,

Varun

Sent from my mobile device, please embrace the typos.

From: Jasper Hale @.> Sent: Monday, July 24, 2023 5:31:24 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14)

Hi Jasper, Last update about NoWakeLock was, you were working on it a stable release soon but due to your health you didn't release it. So just wanted to follow-up on our conversation and check if you made any progress. Regards, Varun Sent from my mobile device, please embrace the typos. ____ From: Jasper Hale @.> Sent: Monday, July 24, 2023 3:32:41 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14https://github.com/Jasper-1024/NoWakeLock/issues/14) why ？ 于 2023年7月24日 UTC 上午9:23:12, Indrasen Pilankar @.> 写到: @Jasper-1024https://github.com/Jasper-1024 hope you are doing well? Just wanted to follow-up on this project. -- Reply to this email directly or view it on GitHub: #14 (comment)https://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1647540088 You are receiving this because you were mentioned. Message ID: @.> -- 使用 K-9 Mail 发送自我的Android设备。 ― Reply to this email directly, view it on GitHub<#14 (comment)https://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1647602888>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UUDYI2I6HQ27K7ZUILXRZB4DANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

I'm very sorry, I misread the github notification email and mistakenly thought it was a spam email. This email did not indicate the context.

At present, I have graduated and left school. My work direction is C language development. The time I can devote to nowakleok is very limited. The progress is not great, but unless there are special reasons, I should continue to work on this project.

— Reply to this email directly, view it on GitHubhttps://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1647774353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UQUCIJEREIWDLC5BU3XRZPZJANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

Jasper-1024 commented 1 year ago

Probably bad news, nowakelock isn't stable enough yet, and that's mostly my problem... I work almost 996 (9am 9pm 6 days a week, just to be clear), so much so that time is really, really scarce and it's hard to carve out time for nowakelock. The fact that it took so long to reply is also the reason, I added a note to the memo, but it didn't work properly that day, so I didn't get back to you in time.

varunpilankar commented 1 year ago

That's real bad news! 😢😔

Hope I could help you out in anyway, I think not.

Guess I'm stuck on A10 forever.

I wish you luck and best wishes.

Regards,

Varun

Sent from my mobile device, please embrace the typos.

From: Jasper Hale @.> Sent: Saturday, August 5, 2023 8:15:37 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14)

Probably bad news, nowakelock isn't stable enough yet, and that's mostly my problem... I work almost 996 (9am 9pm 6 days a week, just to be clear), so much so that time is really, really scarce and it's hard to carve out time for nowakelock. The fact that it took so long to reply is also the reason, I added a note to the memo, but it didn't work properly that day, so I didn't get back to you in time.

— Reply to this email directly, view it on GitHubhttps://github.com/Jasper-1024/NoWakeLock/issues/14#issuecomment-1666524701, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UWQL6HKIHHYIDTYBJDXTZMBDANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

Jasper-1024 commented 1 year ago

That's real bad news! 😢😔 Hope I could help you out in anyway, I think not. Guess I'm stuck on A10 forever. I wish you luck and best wishes. Regards, Varun Sent from my mobile device, please embrace the typos. … ____ From: Jasper Hale @.> Sent: Saturday, August 5, 2023 8:15:37 PM To: Jasper-1024/NoWakeLock @.> Cc: Indrasen Pilankar @.>; Author @.> Subject: Re: [Jasper-1024/NoWakeLock] Migrate from Amplify to NoWakeLock (Issue #14) Probably bad news, nowakelock isn't stable enough yet, and that's mostly my problem... I work almost 996 (9am 9pm 6 days a week, just to be clear), so much so that time is really, really scarce and it's hard to carve out time for nowakelock. The fact that it took so long to reply is also the reason, I added a note to the memo, but it didn't work properly that day, so I didn't get back to you in time. — Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQM6UWQL6HKIHHYIDTYBJDXTZMBDANCNFSM6AAAAAAT5MUN3A. You are receiving this because you authored the thread.Message ID: @.***>

Thank you for your kindness, but it's not that bad. The employment environment in China is very bad this year, we have to work like this to work experience and learn as soon as possible. I think my situation will improve as time goes by. The nowakelock will continue, but there is no guarantee of a specific time node.